|
| Description: |
Add a third value, {{SERVER}}, to the logout endpoint method ({{oidc.endpoint.logout.method}} in xwiki.properties, "Logout endpoint method" in the configuration object), next to the existing {{GET}} and {{POST}}. With it, the RP-initiated logout request is sent by XWiki itself to the provider {{end_session_endpoint}}, as a POST request containing {{id_token_hint}} and (the client being authenticated the same way as for the token endpoint when a secret is configured, otherwise {{client_id}} is sent too) , and XWiki then redirects the browser to the after-logout URL itself.
*This is not standard OpenID Connect.* The [RP-Initiated Logout specification|https://openid.net/specs/openid-connect-rpinitiated-1_0.html] expects the browser to send the logout request: the provider usually identifies the session to end through the cookies the browser sends, and ends the flow by redirecting the browser to {{post_logout_redirect_uri}}. A request sent by XWiki has neither, so it only works with providers which end the session indicated by the ID token passed as {{id_token_hint}}, and the default stays the standard {{GET}} redirect. This option exists because some setups explicitly ask for this behavior.
Things to know when using it: * The request is not sent when no ID token is available, or when it is excluded from the logout request ({{oidc.skipLogoutIdToken}}), since the provider would have no way to know which session to end. * A provider which ignores the request will most probably still answer with a success, so XWiki cannot detect that the user is still logged in on the provider side. * An error answer or a provider which cannot be reached only produces a warning in the log: the user is still logged out from XWiki. |
|