/end-session
Browser logout endpoint for RP-initiated logout.
Endpoint
- Methods:
GETorPOST - URL:
https://sso.user.m7.org/end-session - Response: hosted HTML page
When to use it
Use this endpoint when your application wants to send the user's browser to M7 to end the current SSO session.
Request parameters
id_token_hintrecommendedpost_logout_redirect_urioptionalstateoptionalclient_idoptionallogout_hintoptionalui_localesoptional
Example
https://sso.user.m7.org/end-session?id_token_hint=ID_TOKEN&post_logout_redirect_uri=https%3A%2F%2Fapp.example.com%2Flogout%2Fcallback&state=STATE123
Current behavior
The hosted page:
- inspects the current local M7 session
- validates
id_token_hintwhen present - validates
post_logout_redirect_uriagainst the registered client - asks the user to confirm logout
After logout:
- if a valid post-logout return target is available, the browser is redirected there
- otherwise the browser falls back to
https://www.m7.org
If state was supplied and a validated redirect is used, state is appended to the final return URL.
Redirect validation rules
Current observed rules:
post_logout_redirect_urimust behttps- it must exactly match one of the client's registered
post_logout_redirect_uris - if
post_logout_redirect_uriis sent, M7 needs client context fromclient_idor a validid_token_hint
Notes
- If
id_token_hintis invalid or does not match the suppliedclient_id, the current implementation downgrades to a generic M7 logout flow instead of honoring RP-specific return context. - The legacy
/logoutroute forwards here.