Shibboleth upgrade from V3.3.1 toV3.4.6

REDDIMALLI, ANUSHA REDDIMAA at mailbox.sc.edu
Fri May 22 16:21:40 UTC 2020


All other RelyingPartyByGroup are working which are singing with the same key. Only one particular group has this issue. 

I have verified V3.3.1 configuration in relying-party.xml. It has different provider than others. How can I pass provider value with V3.4.6?

Thanks & Regards
Anusha Reddimalli

-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Peter Schober
Sent: Friday, May 22, 2020 11:12 AM
To: users at shibboleth.net
Subject: Re: Shibboleth upgrade from V3.3.1 toV3.4.6

* REDDIMALLI, ANUSHA <REDDIMAA at mailbox.sc.edu> [2020-05-21 23:20]:
> opensaml::FatalProfileException at (****************************************************)
> 
> Unable to establish security of incoming assertion.

Then your IDP is probably signing with the wrong key.

-peter
-- 
For Consortium Member technical support, see https://protect2.fireeye.com/v1/url?k=05415c8f-5bd70dc9-0541124e-86a279d0e4b2-6f7d87f4fb648736&q=1&e=40d77662-429e-4d41-9213-c9381dc92417&u=https%3A%2F%2Fwiki.shibboleth.net%2Fconfluence%2Fx%2FcoFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net


More information about the users mailing list