Encrypted Assertions and IDP Unsolicited SSO
Cantor, Scott
cantor.2 at osu.edu
Sat Mar 31 18:23:26 BST 2012
On 3/30/12 5:46 PM, "Castellow, Robert" <castellr at musc.edu> wrote:
>This all works if the relying party entry from #1 is never added and the
>defaultRelyingParty for the SAML2SSOProfile type is set to
>encryptAssertions=²never² , but I¹m failing to make this configuration
>vendor specific. What would cause my providerId to be dropped when I add
>this entry to the relying-party.xml?
I can't think of any way that could happen, but if it's reproducible,
there must be a bug in there somewhere. I'm somewhat skeptical though.
-- Scott
More information about the users
mailing list