• Edit a registration form on Layout → Registration forms or create a new registration form
• Scroll down to Username & password creation / Authentication and tick the Enable OAuth checkbox.
• You can configure your own or select one of the predefined OAuth profiles
  • Don't forget to fill in all mandated values

Facebook updated its platform to solve some security issues and now require a strict return URL. This means the oauth return URL should be set to “https://login.fdxtended.com/oauth/callback.php” in the facebook app settings on https://developers.facebook.com. Additionally you need to enable the cookie require checkbox in the registration form.

The subscriber is redirect to the Oauth provider (Facebook, Twitter, …) to sign-in; because the subscriber at that point is still unauthenticated we need to allow the subscriber to visit those websites. Depending on the OAuth provider different domains are required. To enable all HTTP traffic enter 0.0.0.0:80, to do the same for HTTPS traffic enter 0.0.0.0:443. * is the wildcard symbol eg. *.linked.com enables all sub-domains of linked.com.

• www.facebook.com:443
• pixel.facebook.com:443
• fbstatic-a.akamaihd.net:443

• api.twitter.com:443
• www.twitter.com:443
• twimg.com:443
• abs-0.twimg.com:443
• pbs.twimg.com:443

• accounts.google.com:443
• accounts.youtube.com:443
• gstatic.com:443
• ssl.gstatic.com:443
• lh5.googleusercontent.com:443

• licdn.com
• api.linkedin.com:443
• www.linkedin.com:443
• static.licdn.com:443

Usually an OAuth provider allows you to harvest the social profile of your subscriber for data. Typically the returned data depends on the configured scope. This data can be stored in the subscriber profile; to do this enter the returned field name and select the corresponding subscriber profile field from the drop-down. If you need more fields you can add custom input fields and use those.

Scope set to email public_profile

• id
• email
• first_name
• last_name
• gender
• link
• locale
• name
• timezone
• updated_time
• verified

• id
• name
• screen_name
• location
• profile_location
• description
• url
• followers_count
• friends_count
• favourites_count
• statuses_count
• created_at
• utc_offset
• time_zone
• verified
• lang
• status→id
• status→text

• id
• email
• verified_email
• name
• given_name
• family_name
• link
• picture
• locale

• firstName
• lastName
• headline
• id
• siteStandardProfileRequest→url

Note:

• You need multiple registration forms if you desire to use multiple types of OAuth on a single portal. Eg. one registration form for Facebook and one for Twitter.
• Export data collected using registration-form