Configuring SAML2 SSO

This sample is a demonstration on how to configure SAML2 SSO using a sample service provider.

Configuring the web app

1. Check out the source from the repository location which contains the samples.

   svn co http://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/is/4.6.0/modules/samples/sso/

2. Go to <HOME>/sso/SSOAgentSample in the checked out folder and build the sample with following command.

   mvn clean install

3. 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.

   <project xmlns="http://maven.apache.org/POM/4.0.0"
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
            xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
   
   	<groupId>org.wso2.identity</groupId>
   	<version>4.6.0</version>
       <modelVersion>4.0.0</modelVersion>
       <artifactId>wso2is-identity-samples-sso</artifactId>
       <packaging>pom</packaging>
       <name>Identity Server : SSO Samples</name>
   
       <modules>
           <module>SSOAgentSample</module>
       </modules>
   
   </project>

4. After successfully building the sample, a .war file named travelocity.com can be found inside the <HOME>/sso/SSOAgentSample/target folder. 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:

   1. Stop the Apache Tomcat server if it is already running.
   2. Copy the travelocity.war file to the <TOMCAT_HOME>/webapps folder.
   3. Start the Apache Tomcat server.

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

1. Start Identity Server and access management console using https://localhost:9443/carbon/
2. Login to management console using default administrator credentials (the username and password are both "admin").
3. In the management console found on the left of your screen, navigate to Main > Manage > SAML SSO.
4. Click on Register New Service Provider. 
5. A form appears. Register the new service provider by providing the following values.
   

   • Issuer: travelocity.com

     This value should be same as the SAML.IssuerID value specified inside the travelocity.com/WEB-INF/classes/travelocity.properties file.

   • Assertion Consumer URL: http://localhost:8080/travelocity.com/samlsso-home.jsp

     This value should be same as the SAML.ConsumerUrl value mentioned inside the travelocity.com/WEB-INF/classes/travelocity.properties file.

   • NameID format: Enter the default value here (i.e., urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress)
   • 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 = wso2carbon)
   • Enable Single Logout: Set this as true by selecting the checkbox
6. After providing above values click Register.

After successfully registering the service provider, logout from management console. You have now configuring Identity Server as the identity provider. The next step is to run the sample.

Running the sample

1. Visit http://localhost:8080/travelocity.com. You are directed to the following page:
    
2. 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.
3. Enter the default admin credentials (admin/admin).
4. Now you are logged in and you can see the home page of the travelocity.com app.