This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| user_guide:social_login [2019/06/11 09:21] – [Facebook side] admin | user_guide:social_login [2019/06/25 13:53] (current) – [Facebook side] admin | ||
|---|---|---|---|
| Line 41: | Line 41: | ||
| ====== The user used for the temporary session ====== | ====== The user used for the temporary session ====== | ||
| - | * Because we can make use of multiple providers we decided to rather not going the route of providing a large and ever changing list in the Walled | + | * Because we can make use of multiple providers we decided to rather not going the route of providing a large and ever changing list in the Walled |
| * We make use of a temporary user account which will log the user into the captive portal and then redirect them to the authentication provider' | * We make use of a temporary user account which will log the user into the captive portal and then redirect them to the authentication provider' | ||
| * You can choose per Dynamic Login Page which temporary user to use. | * You can choose per Dynamic Login Page which temporary user to use. | ||
| Line 88: | Line 88: | ||
| ===== Facebook side ===== | ===== Facebook side ===== | ||
| * Active the Developer side of Facebook and create a Facebook application. ([[https:// | * Active the Developer side of Facebook and create a Facebook application. ([[https:// | ||
| - | * Go to the **Settings** of the application and specify the URL of the server where you will serve the login pages from. | ||
| - | * Beware that Facebook require that the redirected URL be precisely the same as the one specified. This means that if your login page on the captive portal looks like http:// | ||
| - | {{ : | + | * Below you can see how it looks when we have not yet defined any applications. Go to **My Apps** -> **Create New App**. |
| - | * Record the application' | + | |
| - | * Select | + | {{: |
| + | |||
| + | | ||
| + | |||
| + | {{: | ||
| + | |||
| + | * You will also be required to verify that you are human | ||
| + | |||
| + | {{: | ||
| + | |||
| + | * Facebook will now generate your App with a unique ID which you will later use in RADIUSdesk' | ||
| + | * The App itself will have settings which you can access. Under the **Basic** settings you will find the **App Id** and **App Secret**. | ||
| + | * Record the application' | ||
| + | |||
| + | {{: | ||
| + | |||
| + | * You can now go to the **Products** menu in the bottom left. Click on add a **Product**. We need to add **Facebook Login**. This product will allow for **OAuth2** based authentication which is what we need for Social Logins. | ||
| + | |||
| + | {{: | ||
| + | |||
| + | * Ignore the **Quickstart** options | ||
| + | |||
| + | {{: | ||
| + | |||
| + | * Facebook tighten their security a lot and one now have to explicitly specify the URL's which OAuth will redirect back to. (Our RADIUSdesk server) | ||
| + | * They also force you to use **https** on the server you specify that you will be redirecting back to. | ||
| + | * Our server here is **dev.radiusdesk.com**. Please change this in order to fit your environment. | ||
| + | * The URI in our deployment is https:// | ||
| + | * This is the value we specify in the **Valid OAuth Redirect URIs** | ||
| + | |||
| + | {{: | ||
| + | |||
| + | * After you saved this there is one item outstanding before you can configure the RADIUSdesk side. | ||
| + | * Top left is a switch to take the App out of development | ||
| <WRAP center round alert 90%> | <WRAP center round alert 90%> | ||
| - | Failing to make the application | + | Failing to make the application |
| </ | </ | ||
| - | {{ : | ||