Skip to main content

SAML2 IdP Initiated Single Logout with WSO2 Identity Server 5.1.0


With this feature WSO2 Identity Server facilitates IdP initiated SAML2 single log out requests.

In the SAML service provider configuration UI here is a new configuration called “Enable IdP Initiated SLO”. You can enable this feature using this checkbox. Also you can define redirect URL after the single log out using "Return to URL" under “Enable IdP Initiated SLO” option.


Following parameters can be used with IdP initiated SLO request.

Parameter Description
slo This is a mandatory parameter and must have the value “true” to mark the request as an IdP initiated log out request.
spEntityID This is an optional parameter. Value of the parameter should be the SAML issuer name as in “Issuer” field in the SAML service provider configuration UI.
returnTo This is an optional parameter. Value of the parameter should be the URL which needs to be redirected to, after the log out.
If this parameter is present in the request, ‘spEntityID’ parameter MUST be also present.
Since this needs to be a trusted location, value comes with the request must match with one of the assertion consumer URLs or return to ULRs of the service provider.

Possible log out requests are as follows,
 
1. https://localhost:9443/samlsso?slo=true

When IS received this request, it will send log out requests to all service providers in the session and will redirect to the ‘https://<IS_SERVER>:9443/authenticationendpoint/samlsso_logout.do’ page. This page is the default log out page of the identity server.

2. https://localhost:9443/samlsso?slo=true&spEntityID=travelocity.com

Since this request has mentioned SAML2 service provider name, IS will validate it and will send log out requests to its federated IDPs if available. Then IS will send logout requests to all service providers in the session and will redirect to the 'https://<IS_SERVER>:9443/authenticationendpoint/samlsso_logout.do' page.

3. https://localhost:9443/samlsso?slo=true&spEntityID=travelocity.com&returnTo=https://localhost:8080/avs.com/slo

This request is similar to 2nd request, but we have ‘returnTo’ parameter in the request. In this case after completing similar flow as in 2nd request, IS will redirect to the URL which comes in the ‘returnTo’ parameter. This ‘retrunTo’ value need to matched with one of the ACS URLs or Return To URLs available in the SAML2 service provider configuration.

Labels:

Comments

Post a Comment

Popular posts from this blog

UUID Generation with WSO2 ESB

There are use cases which we need to generate a UUID( universally unique identifier ) from the WSO2 ESB server for the back end services. There are two commonly used UUID types, Version 1 UUID or Time UUID A Version 1 UUID use a scheme relying only on timestamp and the MAC address of the computer on which it is generated Version 4 UUID Version 4 UUIDs use a scheme relying only on random numbers Getting a version 4 UUID is really easy in ESB, since we already have one in the message flow. So we can extract it like follows, <property name="MessageID" expression="fn:substring-after(get-property('MessageID'), 'urn:uuid:')"/> But in case of version 1 UUID or Time UUID, we have to use script mediator or class mediator to generate a UUID . Script mediator is slower compared to the class mediator.  A simple class mediator which can use for version 1 UUID generation can be found here . This class mediator uses this library to gene...
Post a Comment
Read more

How to extract and import certificate from a SAML SP metadata file to a Keystore

Extract certificate from the SAML service provider metadata file as follows, <X509Data> <X509Certificate> MIICNTCCAZ6gAwIBAgIES343gjANBgkqhkiG9w0BAQUFADBVMQswCQYDVQQGEwJVUzELMAkGA1UE CAwCQ0ExFjAUBgNVBAcMDU1vdW50YWluIFZpZXcxDTALBgNVBAoMBFdTTzIxEjAQBgNVBAMMCWxv Y2FsaG9zdDAeFw0xMDAyMTkwNzAyMjZaFw0zNTAyMTMwNzAyMjZaMFUxCzAJBgNVBAYTAlVTMQsw CQYDVQQIDAJDQTEWMBQGA1UEBwwNTW91bnRhaW4gVmlldzENMAsGA1UECgwEV1NPMjESMBAGA1UE AwwJbG9jYWxob3N0MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCUp/oV1vWc8/TkQSiAvTou sMzOM4asB2iltr2QKozni5aVFu818MpOLZIr8LMnTzWllJvvaA5RAAdpbECb+48FjbBe0hseUdN5 HpwvnH/DW8ZccGvk53I6Orq7hLCv1ZHtuOCokghz/ATrhyPq+QktMfXnRS4HrKGJTzxaCcU7OQID AQABoxIwEDAOBgNVHQ8BAf8EBAMCBPAwDQYJKoZIhvcNAQEFBQADgYEAW5wPR7cr1LAdq+IrR44i QlRG5ITCZXY9hI0PygLP2rHANh+PYfTmxbuOnykNGyhM6FjFLbW2uZHQTY1jMrPprjOrmyK5sjJR O4d1DeGHT/YnIjs9JogRKv4XHECwLtIVdAbIdWHEtVZJyMSktcyysFcvuhPQK8Qc/E/Wq8uHSCo= </X509Certificate> </X509Data> Copy extracted certificate to ...
Post a Comment
Read more