Hi there,
Let's try to deduce the problem together!
I see you already highlighted the error area around either:
- *Signature is not trusted*
- *Delegated authentication has failed with client SAML2Client*
- *Ignoring the received exception due to a type mismatch*
*- 500 server error*
Usually the first error is the real error, so that's means *Signature is
not trusted* is most likely the reason the error trigger.
Let try making the application work by disabling the signature
verification, then after all is ok, and try to implement back the signature
verification,
so can you try the following:
*SAML2Client-123456788.json*
{
"@class" : "org.apereo.cas.support.saml.services.SamlRegisteredService",
"serviceId" : "^https://www.example.com/cas/.*
<https://ebt-platform-cas-west.development.dev.ebt.inmar.com/cas/.*>",
"name" : "SAML2Client",
"id" : 123456788,
"evaluationOrder" : 10,
"metadataLocation": "/etc/cas/config/sp-metadata.xml"
"signResponses": false
}
If that also failed, you can also tried other combination of configuration
in the documentaion here:
https://apereo.github.io/cas/5.3.x/installation/Configuring-SAML2-Authentication.html#saml-services,
see if setting anyone of them will allow your system to login.
See if settings the above will help you successfully authenticated.
Cheers!
- Andy
P.s. you should also tried Julien solution too, that might also as well :)
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/2962a1ed-0acc-4a6d-8ef1-5dcc16f732e7%40apereo.org.
