Single-sign-on is one of the key features of the WSO2 Identity Server that enables users to access multiple applications using the same set of credentials. Additionally, the user can access all these applications without having to log into each and every one of them individually. So, if users log into application A, for example, they would automatically have access to application B as well for the duration of that session without having to re-enter their credentials.
The profiles specification for Security Assertion Markup Language 2.0 (SAML 2.0) defines single sign-on based on a web browser. This topic provides instructions on how to use the sample available in the WSO2 Identity Server to demonstrate how to configure SSO using SAML 2.0 with a sample service provider.
When running this sample on AS
Both this SSOAgentSample application and WSO2 Application Server contain different versions of the same slf4j jar. As a solution you can select ONE of the following approaches.
- Remove log4j-over-slf4j-1.6.1.jar file from travelocity.com.war/WEB-INF/lib directory and deploy.
<AS_HOME>/repository/conf/tomcat/webapp-classloading-environments.xmlto resolve the
slf4jconflict and restart the WSO2 Application Server. This change is done so as not to expose the
org.slf4j.*package from WSO2 Carbon.
Configuring the SSO web application
To start off, you must obtain and configure the single sign-on sample. The following steps provide instructions on how to do this.
Use SVN to check out the source from the repository location that contains the single sign-on sample.
Remove the parent entry in the pom.xml file that comes along with the sample. The contents of the pom.xml file will look similar to the following.
Alternatively, you can simply replace the existing pom.xml file with the sample pom.xml file.
In your command line, navigate to
<SAMPLE_HOME>/sso/SSOAgentSamplein the folder you checked out and build the sample using the following command. You must have Apache Maven installed to do this (see Installation Prerequisites for the appropriate version to use).
After successfully building the sample, a .war file named
travelocity.comcan be found inside the
targetfolder. Deploy this sample web app on a web container. To do this, use the Apache Tomcat server.
Since this sample is written based on Servlet 3.0 it needs to be deployed on Tomcat 7.x.
Use the following steps to deploy the web app in the web container:
- Stop the Apache Tomcat server if it is already running.
- Copy the
travelocity.warfile to the
- Start the Apache Tomcat server.
Tip: If you wish to change properties like the issuer ID, consumer URL and IdP URL, you can edit the
travelocity.properties file found inside the
travelocity.com/WEB-INF/classes directory. This sample uses the following default values.
|A unique identifier for this SAML 2.0 Service Provider application|
|The URL of the SAML 2.0 Assertion Consumer|
|The URL of the SAML 2.0 Identity Provider|
If you edit the travelocity.properties file, you must restart the Apache Tomcat server for the changes to take effect.
Now that the web app is successfully deployed on a web container; the next step is to configure WSO2 Identity Server as the identity provider.
Configuring WSO2 Identity Server as an identity provider
- Start the Identity Server and access the management console using https://localhost:9443/carbon/
- Log in to the Identity Server using default administrator credentials (the username and password are both "admin").
- In the management console found on the left of your screen, navigate to the Main menu and click Add under Service Provider.
- Expand the Inbound Authentication Configuration section and then expand SAML2 Web SSO Configuration.
- Click Configure. A form appears. Register the new service provider by providing the following values.
This value should be same as the
SAML.IssuerIDvalue specified inside the
Assertion Consumer URL:
This value should be same as the
SAML.ConsumerUrlvalue mentioned inside the
- NameID format: Enter the default value here (i.e.,
- Use fully qualified username in the NameID: Set this as true by selecting the checkbox
- Enable Response Signing: Set this as true by selecting the checkbox
- Enable Assertion Signing: Set this as true by selecting the checkbox
- Enable Signature Validation in Authentication Requests and Logout Requests: Set this as true
- Certificate Alias: Select wso2carbon here
- Enable Single Logout: Set this as true by selecting the checkbox
- After providing above values click Register.
After successfully registering the service provider, log out from management console. You have now configuring Identity Server as the identity provider. The next step is to run the sample.
Running the sample
. You are directed to the following page:
- Since you need to use SAML2 for this sample, click the first link, i.e., Click here to login with SAML from Identity Server. You are redirected to the Identity Server for authentication.
- Enter the default admin credentials (admin/admin).
- Now you are logged in and you can see the home page of the travelocity.com app.
If you need to view the SAML request and response, please add the following debug log to the
log4j.propertiesfile found inside
- Since single log out is enabled, if you click the logout button in the travelocity.com home page, you will successfully log out.