CAS 5.1.0-RC2 SAML2 IdP failed to locate the matching service metadata when handling LogoutRequest

[Gang Yang]

Hi,

I'm using CAS 5.1.0-RC2 as SAML2 IdP deployed into an external Tomcat 8. I found that CAS fails to locate the matching service metadata when there's more than one SAML services defined. Here's the scenarios:

With two SAML services defined, after logging into one of the service, logout from it, CAS IdP failed to the logout with an error:

java.lang.RuntimeException: Cannot find entity https://ts3.security.army.mil/TS3WebApp in metadata p
rovider.

...

With the debug turned on, it looks like CAS did locate the right service metadata, but somehow did not use it and  continued on to locate the second and wrong service metadata. Of course it would find the entity id there.

However, if I delete the second service definition, the LogoutRequest was handled w/o error - even though it did not work as expected - see a separate topic.

Attached is the Tomcat console log with debug turned on for org.apereo. Look for "Start of SLO".

Appreciate any help!

Gang

[Gang Yang]

Please use this more recent log file. The previous log file did not seem to show that two service metadata were searched.

Gang

[Misagh Moayyed]

File an issue please. 

-- 
Misagh

--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
---
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 cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/cf0077f8-4364-4c66-9ec4-39b71838634d%40apereo.org.