Shibboleth exception - Could not resolve placeholder 'idp.sealer.keyPassword'

[Punjabi, Puneet]

Thanks Kevin for the prompt response. 
I believe I am using Shibboleth v2.0 as I am following the instructions on wiki page - https://wiki.shibboleth.net/confluence/display/SHIB2/IdPInstall
Do I still need Tomcat 7.0 / 8.0?

I verified that tomcat has file access permissions to the shibboleth files in IDP_HOME directory as it parsing the global-system.xml file while encountering the error.

Thanks & Regards
Puneet

-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Kevin Foote
Sent: Monday, March 23, 2015 4:37 PM
To: Shib Users
Subject: Re: Shibboleth exception - Could not resolve placeholder 'idp.sealer.keyPassword'


> On Mar 23, 2015, at 4:27 PM, Punjabi, Puneet <Puneet.Punjabi at sagitec.com> wrote:
> 
> Hello,
> 
> I have successfully installed Shibboleth v2.0 on Windows 2012 server. 

I believe you mean V3 :)

> However, when I start the idp application in Tomcat (v6.0) I get the 
> following exception in the tomcat log file -

Tomcat 6 is not supported try Tomcat 7 or 8. 
See <https://wiki.shibboleth.net/confluence/display/IDP30/SystemRequirements>

> Mar 23, 2015 5:18:04 PM org.apache.catalina.core.StandardContext 
> listenerStart
> SEVERE: Exception sending context initialized event to listener 
> instance of class 
> org.springframework.web.context.ContextLoaderListener
> org.springframework.beans.factory.BeanDefinitionStoreException: 
> Invalid bean definition with name 'shibboleth.DataSealerKeyStrategy' 
> defined in file
> [C:\Progra~2\Shibboleth\IdP\system\conf\global-system.xml]: Could not 
> resolve placeholder 'idp.sealer.keyPassword' in string value "%{idp.sealer.keyPassword}"; nested exception is java.lang.IllegalArgumentException: Could not resolve placeholder 'idp.sealer.keyPassword' in string value "%{idp.sealer.keyPassword}”….
> 
> I have confirmed that the attributes are defined in the IDP_HOME/conf/idp.properties file. 
> 
> # Settings for internal AES encryption key idp.sealer.storeType = 
> JCEKS idp.sealer.updateInterval = PT15M idp.sealer.aliasBase = secret 
> idp.sealer.storeResource= %{idp.home}/credentials/sealer.jks
> idp.sealer.versionResource= %{idp.home}/credentials/sealer.kver
> idp.sealer.storePassword= {29FC5957-F93F-43DF-8FAF-BEF8156F9EA9}
> idp.sealer.keyPassword= {29FC5957-F93F-43DF-8FAF-BEF8156F9EA9}
> 
> Therefore, I believe that the application is unable to access or reference the properties file.

Also have you verified that your windows permissions allow access to this file? 
I’m not a window person but I believe that permissions need to allow access to these files for whoever is running the tomcat process.

--------
thanks
 kevin.foote

--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net