| Note | |
|---|---|
| title | Advanced ConfigurationNote, this is an advanced configuration feature. Most deployments can rely on the shorthand elements. |
...
If the message is a request via a front-channel binding, then the following steps are performed. If an error occurs at any point, an effort is made to respond to the requesting IdP with a <samlp:LogoutResponse>containing the error.
Verification of the information in the request against the active session is done.
Any of this user's sessions being logged out other than the active session are removed from the cache.
Front and back-channel application notification loops are executed.
A
<samlp:LogoutResponse>is returned to the requesting IdP. The status indicates whether the SP believes that the logout completely succeeded.
If the message is a request via a back-channel binding, then the following steps are performed:
The request content is used to obtain a list of applicable sessions to remove.
The sessions are removed.
The back-channel application notification loop is executed.
A
<samlp:LogoutResponse>is returned to the requesting IdP. The status indicates whether the SP believes that the logout completely succeeded.
If the message is a response, then the SP completes the logout operation by redirecting to the browser to a location preserved by relay state, if any, or the globalLogout template is displayed.
The following Binding values are supported:
urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirecturn:oasis:names:tc:SAML:2.0:bindings:HTTP-POSTurn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST-SimpleSignurn:oasis:names:tc:SAML:2.0:bindings:HTTP-Artifacturn:oasis:names:tc:SAML:2.0:bindings:SOAP
Attributes
| Include Page | ||||
|---|---|---|---|---|
|