Shib 3.2.1

[Cheltenham, Chris]

Peter,

Thanks you have validated anything I have thought.
I was wondering if I missed anything.

20 other vendors are already working fine with the certs in the metadata.

I am not sure what else to tell them except look at the test server that
works and see why production isn't.

Everything on my side is being used by multiple other vendors just fine.


===========================

Thank You;

Chris Cheltenham
Technology Services
The School District of Philadelphia

Work # 215-400-5025
Cell # 215-301-6571 

-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Peter Schober
Sent: Monday, June 18, 2018 9:15 AM
To: users at shibboleth.net
Subject: Re: Shib 3.2.1

* Cheltenham, Chris <ccheltenham-ext at philasd.org> [2018-06-18 15:01]:
> I am releasing assertions to our vendor's SP however they get an error 
> saying.
> 
> "Details: Signature used for attempting SSO is invalid."

That's not an error message from the Shibboleth software, AFAIK, and it's
also not a particularly helpful one at that.
So for details about what exactly this means you'd have to ask the vendor.

If that means they think the signature on the SAML you sent them is
"invalid" you probably gave them the wrong certificate for verifying those
signatures.
If you gave them SAML 2.0 Metadata (and not a certificate separately)
maybe they extracted the wrong cert from the metadata.

-peter
--
For Consortium Member technical support, see
https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to
users-unsubscribe at shibboleth.net