Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Adapt CAS logout propagation flow for initiation from SOAP logout
Description fields
Basics
Logistics
Basics
Logistics
Description
I was able to design the SOAP logout machinery to reuse the existing logout propagation flow(s) we designed for the front-channel case, but the CAS propagator is currently front-channel oriented even though it's a back-channel logout since it uses javascript to drive the process.
I think it should be possible to redo it as just a pre back-channel that reports its result in its response view like I did with the SAML SOAP case and then it should work either way so this is a task for that work.
I was able to design the SOAP logout machinery to reuse the existing logout propagation flow(s) we designed for the front-channel case, but the CAS propagator is currently front-channel oriented even though it's a back-channel logout since it uses javascript to drive the process.
I think it should be possible to redo it as just a pre back-channel that reports its result in its response view like I did with the SAML SOAP case and then it should work either way so this is a task for that work.