Repository navigation
Replies: 5 comments 7 replies
|
We (https://github.com/cloudtrust) need to have proper backchannel logout through SOAP binding soon. So we propose to start working on this feature, and collect your feedback as soon as we have something ready for you to look at (same we did while developing the Artifact binding feature). Thanks! |
AFAIK, only historical, there is no support for SOAP in Keycloak SAML adapters so I believe it had to use POST. We would be happy to have at least server part done correctly. |
|
I'm back on the topic, currently working on the implementation of SOAP binding for SAML logout. Now, question: shall I clean the current implementation of backchannel logout and align it with the SAML specification (SOAP only), or shall I only add the correct way and keep the current behavior as an option? |
|
@mhajas |
|
Thank you for the reminder to close this @codespearhead! |
Uh oh!
There was an error while loading. Please reload this page.
Hello,
We have a need to support SAML Single-logout through backchannel with SOAP binding:
After some analysis of what is offered by Keycloak, I came to the conclusion that:
We would like to work on a PR to add the support of the SOAP binding for the SAML single logout functionality.
First, I'd need some additional information on the current implementation:
Is there any reason why the backchannel logout was implemented like this in Keycloak?
It does not seem to comply with the SAML specification, as the only backchannel binding is the SOAP binding [1]
Thanks!
[1] https://docs.oasis-open.org/security/saml/v2.0/saml-profiles-2.0-os.pdf, section 4.4.3
All reactions