Social WiFi Captive Portal with FortiAuthenticator (Twitter)

Facebooktwittergoogle_plusredditpinterestlinkedinFacebooktwittergoogle_plusredditpinterestlinkedin

WiFi authentication using social media provides access control without having to manually create guest accounts.

This recipe involves configuring an API for Twitter accounts, setting up a social portal RADIUS service on the FortiAuthenticator, and configuring the FortiGate for Captive Portal access.
 
This recipe is similar to the Captive portal WiFi access control recipe, but involves external security mode configuration, RADIUS authentication, and does not include FortiAP registration instructions.
 
Note that some minimal CLI usage is required when configuring the FortiGate.
 
The FortiAuthenticator has been given an example fully qualified domain name (FQDN) — fortiauthenticator.example.com.

1. Configuring the Twitter developer account API

Open a browser and log in to your Twitter account. In the URL field enter the following:

https://apps.twitter.com/

Select Create New App.

Enter a Name, Description, and Website for the application.

In the Callback URL field, enter the following:

https://fortiauthenticator.example.com/social/complete/twitter/

Note that the FortiAuthenticator needs to be able to access the Internet.

Accept the Developer Agreement and select Create your Twitter application.

Go to Keys and Access Tokens to view your Consumer Key and Consumer Secret.

Take note of the Consumer Key and Consumer Secret as they are required when configuring the Captive Portal on the FortiAuthenticator.

The Consumer Key and Consumer Secret can be accessed at any time on the Twitter developer account, but it may be a good idea to copy them to a secure location.

2. Configuring the social portal RADIUS service on FortiAuthenticator

On the FortiAuthenticator, go to Authentication > User Management > User Groups, and create a Social_Users user group.

Users that log into Twitter will be placed in this group once it is added to the Captive Portal General Settings.

 

Go to Authentication > RADIUS Service > Clients, and create a new RADIUS client.

Enter a Name for the RADIUS client (the FortiGate) and enter its IP address (in the example, 172.20.121.56).

Enable the Social portal captive portal.

 

Enter the pre-shared Secret and set the Authentication method. The FortiGate will use this secret key in its RADIUS configuration.

Add the Social_Users user group to the Realms group filter as shown.

Select Save and then OK.

Next go to Authentication > Captive Portal > General and enable Social Portal.

Configure the account expiry time (in the example it is set to 1 hour).

Set Place registered users into a group to Social_Users.

Enable the Twitter login option and add your Twitter Consumer Key and Consumer Secret.

3. Configuring the FortiGate authentication settings

On the FortiGate, go to User & Device > Authentication > RADIUS Servers and create the connection to the FortiAuthenticator RADIUS server, using its IP and pre-shared secret.

Use the Test Connectivity option with valid credentials to test the connection.

Next, go to User & Device > User > User Groups and create a RADIUS user group called social_users.

Set the Type to Firewall and add the RADIUS server to the Remote groups table.

4. Configuring the FortiGate WiFi settings

Go to WiFi & Switch Controller > WiFi Network > SSID and select the SSID interface.

Under WiFi Settings, set the Security Mode to Captive Portal.

For the Authentication Portal, select External, and enter the FQDN of the FortiAuthenticator, followed by /social_login/.

For this recipe, it is set to:

https://fortiauthenticator.example.com/social_login/

Set User Groups to the social_users group.

5. Configuring the FortiGate to allow access to Twitter

On the FortiGate, configure firewall addresses to allow users to access the Twitter login page.

The following step can be performed in the GUI, but may take considerably longer than using the CLI. You can also copy and paste the commands below into the CLI console.

Go to System > Dashboard and enter the CLI Console. Enter the following, which creates the firewall addresses and adds them to a firewall address group called Twitter_Auth:

config firewall address
   edit "api.twitter.com"
      set type fqdn
      set fqdn "api.twitter.com"
   next
   edit "abs.twimg.com"
      set type fqdn
      set fqdn "abs.twimg.com"
   next
   edit "abs-0.twimg.com"
      set type fqdn
      set fqdn "abs-0.twimg.com"
   next
end
config firewall addgrp
   edit "Twitter_Auth"
      set member "api.twitter.com" "abs.twimg.com" "abs-0.twimg.com"
   next
end

Go to Policy & Objects > Policy > IPv4 and create a policy for Twitter authentication traffic.

Set Incoming Interface to the WiFi SSID interface and set Source Address to all.

Set Outgoing Interface to the Internet-facing interface and set Destination Address to Twitter_Auth.

Set Service to ALL and enable NAT. Configure Security Profiles accordingly.

Go to System > Dashboard and enter the CLI Console. Add the following to exempt the Twitter authentication traffic policy from the captive portal:

config firewall policy
   edit <policy_id>
      set captive-portal-exempt enable
   next
end

This command allows access to the external Captive Portal.

6. Configuring the FortiGate to allow access to FortiAuthenticator

On the FortiGate, go to Policy & Objects > Objects > Addresses and add the FortiAuthenticator firewall object.

For Subnet/IP Range enter the IP address of the FortiAuthenticator.

Go to Policy & Objects > Policy > IPv4 and create the FortiAuthenticator access policy.

Set Incoming Interface to the WiFi SSID interface and set Source Address to all.

Set Outgoing Interface to the Internet-facing interface and set Destination Address to FortiAuthenticator.

Set Service to ALL and enable NAT.

Add the following to exempt the FortiAuthenticator access policy from the Captive Portal:

config firewall policy
   edit <policy_id>
      set captive-portal-exempt enable
   next
end

7. Results

Connect to the WiFi and attempt to browse the Internet. You will be redirected to the Captive Portal splash page.

Select Twitter and you should be redirected to the Twitter login page.

Enter valid Twitter credentials and you will be redirected to the URL initially requested.

You can now browse freely until the social login account expires, as configured on the FortiAuthenticator under Authentication > Captive Portal > General.

To view the authenticated user added on FortiAuthenticator, go to Authentication > User Management > Social Login Users.

You can configure Captive Portal to use other social WiFi logins:

Keith Leroux

Keith Leroux

Technical Writer at Fortinet
Keith Leroux is a writer on the FortiOS 'techdocs' team in Ottawa, Ontario. He obtained a Bachelor's degree from Queen's University in English Language and Literature, and a graduate certificate in Technical Writing from Algonquin College. He spent a year teaching ESL in South Korea. Annyeong!
Keith Leroux

Latest posts by Keith Leroux (see all)

  • Was this helpful?
  • Yes   No
  • Panos

    Hi Keith,
    Is it possible somehow to export in a readable format a user list that logged in via the social wifi ?

    • Keith Leroux

      Hi Panos,

      I’m not familiar with a method to export purely social-wifi logins, but you can filter in the User Events log for users and/or user groups.

      • Panos

        Hi Keith,
        I saw this option too. I believe FAC should have an option for reporting (*even if FAZ should be used instead)
        Thank you for you prompt reply

        Best Regards
        Panos