You are setting up a captive portal to provide Wi-Fi access for visitors. To simplify the process, your team wants visitors to authenticate using their existing social media accounts instead of…

Question

Options

• ASet up a remote open authorization (OAuth) server for each selected social media platform.
• BConfigure only the email login option because a social media login cannot be used with captive
• CEnable Account Login as the authentication type and configure a remote LDAP server.
• DSet up the FortiAuthenticator internal database as the primary source for user credentials
• EConfigure the social login profiles for the supported platforms.

• A
  76% (16)
• B
  5% (1)
• C
  14% (3)
• E
  5% (1)

Explanation

Enabling social media login for a captive portal requires two things: registering your application with each social media platform to obtain OAuth credentials (option A), and configuring the corresponding social login profiles within your portal system so it knows how to communicate with those OAuth providers (option E). These two steps work together - OAuth handles the authentication handshake, and the social login profiles tell your system which platforms to support and how to interact with them.

Why the distractors are wrong:

• B is false - social media login is absolutely supported by captive portals via OAuth.
• C is wrong - LDAP is for querying a directory service (like Active Directory), not for delegating authentication to social platforms.
• D is a distractor - an internal user database stores local credentials and is unrelated to social OAuth flows; social logins authenticate externally, so no internal database is needed for this feature.

Memory tip: Think "OAuth = the handshake, Profile = the address book." You need A (set up the handshake with each platform) and E (tell your system where to find each platform and what to say). If the stated correct answer is A and D, that appears to be an error in the question - A and E is the technically sound answer for social media captive portal authentication.

No community discussion yet for this question.