services.hope.pidservice.url=https://pid.socialhistoryservices.org/
services.hope.pidservice.endpoint=${services.hope.pidservice.url}/secure 
services.hope.pidservice.wsdl=classpath:/org/socialhistoryservices/pid/pid.wsdl
services.hope.pidservice.ns=http://pid.socialhistoryservices.org/
services.hope.pidservice.name=PidResourceService
#use this account to get a pid service account to ask for a web service key
services.hope.pidservice.remote.account.user=isti.cnr
services.hope.pidservice.remote.account.pwd=istiCnr
#use the webservice key to be client of the IISG PID service on https:
#Place the key in a HTTP header request as expressed in this pseude code:
#HTTP-header("Authorization", "oauth ab45143f-9748-4c5c-b2f0-4f39fbe3debf")
#allowed naming authority (for test purpose only): 12345 and 12345.1 (the latter allows pid deletion)
service.hope.pidservice.remote.wskey=oauth f5270cfd-04bb-4b82-86a3-a9bf15a03a31

#seems we need to put the trustStore path and password directly in the configuration because properties are not resolved in the configuration.
service.hope.pidservice.trustStore.path=classpath:/eu/dnetlib/pid/trust
service.hope.pidservice.trustStore.pwd=pidPwd

service.hope.pidservice.resolveURL.default=https://aggregator.socialhistoryservices.org/unavailable.html