Could not resolve a key encryption credential for peer entity
Fong, Trevor
trevor.fong at ubc.ca
Fri Sep 23 20:31:50 BST 2011
Thanks everyone for your suggestions. Several of you were right - the entity ID did not match. Stupid mistake on my part - there was a trailing slash in the deployed version that was not present in the SVN version that I was working off.
Trev
-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Peter Schober
Sent: September-23-11 9:57 AM
To: users at shibboleth.net
Subject: Re: Could not resolve a key encryption credential for peer entity
* Fong, Trevor <trevor.fong at ubc.ca> [2011-09-23 18:38]:
> In relying-party.xml, I've specified <AnonymousRelyingParty>, then
> <DefaultRelyingParty> and then <RelyingParty
> id="https://ubctest.service-now.com"> - is that the correct place to
> put it? I tried specifying it before AnonymousRelyingParty and also
> between AnonymousRelyingParty and DefaultRelyingParty but the IdP
> didn't seem to like either situation and wouldn't start.
Yes, it's a sequence, cf. shibboleth-2.0-relying-party.xsd -peter
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users
mailing list