Enabling social media login for a captive portal on FortiAuthenticator involves two primary configuration steps. First, an administrator must register the FortiAuthenticator as an authorized application within each respective social media platform's developer portal (such as Google Cloud Platform or Meta for Developers). This external setup is necessary to obtain the OAuth Client ID and Client Secret. This action corresponds to setting up the connection to the remote OAuth server. Second, using these credentials, the administrator must configure a corresponding "Social Login Profile" on the FortiAuthenticator. This profile allows FortiAuthenticator to act as an OAuth client and properly redirect users to the social media provider for authentication.

B. This is incorrect because FortiAuthenticator natively supports social media logins for captive portals; it is not limited to email-only options.

C. LDAP is a protocol for authenticating against enterprise directory services (like Active Directory), which is a different mechanism than social media OAuth-based logins.

D. For social media logins, the primary source of user credentials is the external social media provider, not the FortiAuthenticator's internal user database.

1. FortiAuthenticator 7.2 Administration Guide, Page 141, "Social Wi-Fi login".

The section explicitly states: "Before you can configure social login profiles on FortiAuthenticator, you must first configure your social network accounts to allow FortiAuthenticator to act as an authentication agent." This supports the action described in option A, which is the setup on the remote platform that provides the OAuth service.

The guide continues on page 142, "To configure a social login profile on FortiAuthenticator:", detailing the steps to create the profile using the Client ID and secret obtained from the social media provider. This directly supports option E.

2. FortiAuthenticator 7.2 Administration Guide, Page 141, "Social Wi-Fi login" diagram.

The workflow diagram clearly shows the "Social Network" (e.g., Google, Facebook) as the "OAuth Server" and the FortiAuthenticator as the "OAuth Client," validating that the interaction is with a remote OAuth server and that profiles must be configured on FortiAuthenticator to manage this client role.