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.
...
| Excerpt |
|---|
- Go to https://developers.facebook.com/ and log in using your Facebook credentials.
- Click on Create App.
 - Enter a Display Name, Contact Email, and click Create App ID.
 - Enter code for security check, and click Submit.
- On Select product page, click Set up under Facebook Login.
 - Select Website as the platform for the app used in this sample.
 Enter https://localhost:9443/ as the Site URL and click Save. 
Under Products on the left navigation panel, Click Facebook Login. You can configure the Client OAuth Settings on the window that appears.
 - Client OAuth Login should be set to Yes.
Client OAuth Login is the global on-off switch for using OAuth client token flows. It helps to secure your application and prevent abuse by locking down which token redirect URIs are allowed. - Web OAuth Login should be set to Yes.
Web OAuth Login settings enables any OAuth client token flows that use the Facebook web login dialog to return tokens to your own website. Valid OAuth redirect URIs should be set to https://localhost:9443/commonoauth.
Enter the ACS URL (Assertion Consumer URL) which is the endpoint in WSO2 Identity Server which accepts the response sent by facebook.
Scroll down and click Save Changes button to save the changes. Click on Dashboard. You can see the App ID and App Secret as shown in the image below. Click Show to view the App Secret. | Info |
|---|
App ID is the Client ID and the App Secret is the Client Secret in OAuth terminology. The API Version is Facebook’s API that is used to create the application. |
Click Settings on the left menu and navigate to the Basic tab. Add the App Domains (since WSO2 IS is running on localhost, you can add localhost as the App Domain) Click Save Changes.
Now you have finished configuring Facebook as an Identity Provider. | Info |
|---|
| title | About accessing the app |
|---|
| The app is not available to general public yet. To make to app available to every Facebook user, you have to submit the app for review. After a review, Facebook makes the app available to every Facebook user. You can find more information on the review process by clicking on App Review in the left navigation menu of your app's dashboard. The review process may take some time, so for the purposes of this sample, you can specify some Facebook users as Developers or Testers. Only the users specified here can use this app to log in with Facebook until the app goes public. To do this, click on Roles in the left navigation menu of the dashboard and specify the required Facebook users as Developers or Testers. 
|
|
...
Open a terminal window and add the following entry to the /etc/hosts file of your machine to configure the hostname.
| Code Block |
|---|
|
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 |
|
- Deploy this sample web app on a web container.
- Use the Apache Tomcat server to do this.
- Since this sample is written based on Servlet 3.0, it needs to be deployed on Tomcat 7.x.
Copy the .war file into the webapps folder. For example, <APACHE_HOME>/apache-tomcat-7.0.50/webapps.
- Start the tomcat server.
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 |
|---|
|
#The URL of the SAML 2.0 Assertion Consumer
SAML2.AssertionConsumerURL=http://wso2is.local:8080/travelocity.com/home.jsp |
| Tip |
|---|
Tip: If you wish to change properties like the issuer ID, consumer URL, and IdP URL, you can edit the travelocity.properties file found in the travelocity.com/WEB-INF/classes directory. Also if the service provider is configured in a tenant you can use "QueryParams" property to send the tenant domain. As an example "QueryParams=tenantDomain=wso2.com". This sample uses the following default values. | Properties | Description |
|---|
SAML2.SPEntityId=travelocity.com
| A unique identifier for this SAML 2.0 Service Provider application | SAML2.AssertionConsumerURL=http://wso2is.local:8080/travelocity.com/home.jsp
| The URL of the SAML 2.0 Assertion Consumer | SAML2.IdPURL=https://localhost:9443/samlsso
| The URL of the SAML 2.0 Identity Provider | SAML2.IsPassiveAuthn=true
| Set this to send SAML2 passive authentication requests |
If you edit the travelocity.properties file, you must restart the Apache Tomcat server for the changes to take effect. |
...
You have now added and configured the service provider.
| Note |
|---|
The default client-truststore.jks found in the <IS_HOME>/repository/resources/security/ directory contains the Facebook certificate by default. |
| Panel |
|---|
|
For more information on SSO, see Single Sign-On. |
...