Page Comparison

Current trends require usage of services from hundreds of websites in a connected world. Most of these websites need the user to create an account with them by providing a valid email address and password. Remembering all the different user IDs and passwords that you use can be difficult and cumbersome. To make life easier most websites now provide the user with an option to log in using their Facebook account, Twitter account or Google account. Since most of the internet users have one of these accounts, it makes creating a new account an instant action.

WSO2 Identity Server enables users to log in to applications with their Facebook account. To do that, first you have to create a Facebook app after registering as a Facebook developer.

This topic provides instructions on how to configure the Facebook app and the Identity Server to integrate using a sample app. See the following sections for more information.

Configuring the Facebook app

Deploying travelocity.com sample app

The next step is to deploy the travelocity.com sample app in order to use it in this scenario. Please  

...

...

1. Open a terminal window and add the following entry to the /etc/hosts file of your machine to configure the hostname.

   Code Block
   language bash
   127.0.0.1 wso2is.local

   Info
   title Why is this step needed?
   Some browsers do not allow you to create cookies for a naked hostname, such as localhost. Cookies are required when working with SSO. Therefore, to ensure that the SSO capabilities work as expected in this tutorial, you need to configure the etc/host file as explained in this step. The etc/host file is a read-only file. Therefore, you won't be able to edit it by opening the file via a text editor. Instead, edit the file using the terminal commands. For example, use the following command if you are working on a Mac/Linux environment. Code Block sudo nano /etc/hosts

2. Download the travelocity.com.war file from here.
3. Deploy this sample web app on a web container. 
   1. Use the Apache Tomcat server to do this.
   2. Since this sample is written based on Servlet 3.0, it needs to be deployed on Tomcat 7.x.

   3. Copy the .war file into the webapps folder. For example, <APACHE_HOME>/apache-tomcat-7.0.50/webapps.

   4. Start the tomcat server.

4. Open the travelocity.properties file found in the <APACHE_HOME>/webapps/travelocity.com/WEB-INF/classes directory and configure the following property with the hostname (wso2is.local) that you configured above. Finally restart the tomcat server.

   Code Block
   language text
   #The URL of the SAML 2.0 Assertion Consumer SAML2.AssertionConsumerURL=http://wso2is.local:8080/travelocity.com/home.jsp

...

1. Return to the Management Console.
2. In the Identity section under the Main tab, click Add under Service Providers.
3. Enter travelocity.com in the Service Provider Name text box and click Register.
4. In the Inbound Authentication Configuration section, click Configure under the SAML2 Web SSO Configuration section and set the configuration as follows:

   1. Enter the following values:

      Panel
      Issuer: travelocity.com Assertion Consumer URL: http://wso2is.local:8080/travelocity.com/home.jsp

   2. Select the following check-boxes:

      Panel
      Enable Response Signing Enable Single Logout Enable Attribute Profile Include Attributes in the Response Always

   

5. Click Register. Now you will be sent back to the Service Providers page.

6. Go to the Local and Outbound Authentication Configuration section.

7. Select the Federated Authentication radio button and select the Identity Provider you created from the dropdown list under Federated Authentication. 
   Image RemovedImage Added

8. Click Update to save the changes.

You have now added and configured the service provider.

...

Configuring requested claims for travelocity.com (optional)

Generally, the service providers need some information from the Identity Provider side after the authentication process in order to provide their service. To help this process we need to configure the necessary claims on the service provider side.

...

1. In the Identity section under the Main tab, click List under Service Providers.
2. Click Edit to edit the travelocity.com service provider.
3. Go to Claim Configuration.

4. Click on Add Claim URI under Requested Claims to add the requested claims as follows. Here you should add the claims you mapped in the Identity Provider claim configuration. Select the Mandatory Claim checkbox for any claims that are mandatory. 

   Info
   title Do only,
   If the service provider needs any claims to be used after authentication process, the SP can request those claims from IDP as "Requested Claims".

   Image Modified

   Info
   Here, the claims which are marked as mandatory are requested by the service provider from the identity provider. If they are not available, the user will be redirected to a different page to request those mandatory claim values from the user as they are mandatory.

5. Subject Claim URI is the unique claim which we can use to identify a service provider. Therefore, select a suitable claim for the Subject Claim URI such that it will become a unique identifier for the service provider.

6. Click Update to save changes.

...

1. To test the sample, go to the following URL: http://wso2is.local:8080/travelocity.com. 
   
2. Click the link to log in with SAML from WSO2 Identity Server.
3. You are redirected to the Facebook Login page. Enter your Facebook credentials and you will be taken to the home page of the travelocity.com app.