Message was signed, but signature could not be verified
Tejash Mistry
tejash.mistry at fasttrackteam.com
Fri Jul 19 10:32:26 EDT 2013
Hello Scott,
I just want to inform you that IdP's metadata is updated automatically at
our end. I have configured certificate in the Shibboleth2.xml file in
<CredentialsResolver> node.
Thanks & Regards,
Tejash Mistry
Sr. Software Engineer |Fast Track Software Services Pvt Ltd|K6/3 Erandwane,
Pune, India 411004
m: +91.9823.237770|o: +91.20.2544.1522|www.fasttrackteam.com|
-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On
Behalf Of Cantor, Scott
Sent: Friday, July 19, 2013 7:48 PM
To: Shib Users
Subject: RE: Message was signed, but signature could not be verified
> I have configured SP in our environment and it is working fine. Last
> week I have received a mail from one of our Federation that they have
> changed their "Metadata signing certificate" and "SAML IdPs
> signing/encryption certificate". They have provided us both this
> certificate. I have configured it in our environment but it was
> throwing error like "Message was signed, but signature could not be
verified."
Then you didn't configure it. I don't know what you did, but in Shibboleth
it requires updating the IdP's metadata with the certificate(s).
-- Scott
--
To unsubscribe from this list send an email to
users-unsubscribe at shibboleth.net
More information about the users
mailing list