To add some informations from my previous message: - from CAS I have this log : DEBUG [org.apereo.cas.web.flow.DelegatedAuthenticationSAML2ClientLogoutAction] - <The current client is not a SAML2 client or it cannot be found at all, no logout action will be executed.>
after debugging into the code to find if a client is a SAML2Client a profile should be provisionned, but it's not the case so it returns each time a null client. What is missing here ? should a profile be provisionned and how in this case ? Or there is a problem with a wrong check ? I could fix that but let me know what is to good way to do. Thansk Le jeudi 4 juillet 2019 13:16:17 UTC+2, Julien Gribonvald a écrit : > > Hi, > > I can't find in documentation how the logout should work with delegated > Authentification (from pac4j module as example). > > I'm looking on the workflow when the global logout is initiated from the > CAS (or from a service to the CAS), is there a way to propagate it to > the IDP which the user connected ? I can't have this working with a SAML > IDP whereas metadatas have the SLOLogout url information provided. > > Also is it working when the logout request come from the SAML IDP ? > > How this should work, what are the requirements ? I'm using the CAS V6 > master branch. > > Thanks, > > -- > Julien Gribonvald > -- - 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/957dcddb-6704-42bc-8099-4e992fc6152c%40apereo.org.
