Hi Divyesh,
Which CAS version you used?
i have same use-case as you, maybe we can help each other out.
These are my steps:
1. in CAS service management for application A, go to "Logout" tab, and put your application A logout URL there
2. do the same for application B
3. when you execute logout from application A, you also need to trigger SSO logout to your CAS.
and specify where to redirect after SSO logout.
by doing this, you clear application A session, and also clear SSO session in CAS server, and redirect back to your applicationA logout result page
4. do the same for application B.
5. if user logout from application A, CAS will trigger POST message to all application, contain the message below:
<?xml version="1.0" encoding="UTF-8"?>
<samlp:LogoutRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" ID="LR-21-boFjgZjhbGxHprcU6ZFLoDUXtxztpJyswnr" Version="2.0" IssueInstant="2017-11-02T18:10:16Z">
<saml:NameID xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">@NOT_USED@</saml:NameID>
<samlp:SessionIndex>ST-33-e5eu5by9MnAsoZzdsmio-DOMAIN17086</samlp:SessionIndex>
</samlp:LogoutRequest>
please note that for both application A & B, i configured both as OAuth client
i am now stuck in the use-case where user logout from application A will also clear application B session.
- if i logout from application A, CAS successfully send POST message to aplpication B, but the problem is i dont know which session in application B to kill.
as the message above is only contain service ticket.
if both your App A & B is configured as CAS client, then you will be fine.