[V5.0.2 or later]

Using third-party authentication provider credentials to access the Developer Portal

You can use the log in credentials that are used with third-party authentication providers, to access the Developer Portal. Using third-party authentication provider credentials reduces the number of authentication credentials that a user has.

Before you begin

  • You must have administrator access to complete this task.

  • You must be the Owner or Administrator of a Developer organization in the API Manager.

  • Portal Delegated User Registry must be selected in the API Manager UI. For more information, see Portal Delegated User Registry.

  • In order to use third-party authentication provider credentials, the HybridAuth module must be enabled. However, note that you cannot use administrator approval of new accounts with Hybrid Auth.
Important:
  • If the Portal Delegated User Registry is selected for a Catalog, the Developer Portal REST APIs cannot be used to gain access to the content in that Catalog, and portal analytics is disabled. This restriction is because the user management is delegated to the Developer Portal, and consequently the management server can no longer provide user authentication. You also cannot enable two-factor authentication for the Developer Portal.
  • The Portal Delegated User Registry (PDUR) feature is not available in IBM® API Connect Version 2018, as additional user security options are available on the Management server. For a simpler migration process from Version 5 to Version 2018 (when the tooling is available), it is recommended to not use PDUR.

About this task

You can use your third-party authentication provider credentials instead of an LDAP or local user registry. You can specify the use of authentication credentials for the following third-party authentication providers:
  • Facebook
  • Google
  • LinkedIn
  • Windows Live
  • Twitter
  • GitHub
  • Slack
Note: You can enable multiple third-party authentication providers at one time.

Procedure

In the Developer Portal:

  1. Log in as an administrator.
  2. Ensure that the HybridAuth module is enabled. For information about enabling and disabling modules, see Disabling modules.
    When you select Portal Delegated User Registry in the API Manager UI, the module is enabled automatically.
  3. On the administrator dashboard, click Configuration > People > HybridAuth.
  4. From the list of authentication providers that are displayed, click the check box for the authentication provider that has the authentication credentials that you want to use, then click Settings.
    The Application settings tab contains text fields that must be filled with specific values for the authentication provider. Information on obtaining these values can be found in the Obtaining the Application setting values topics for each authentication provider, which are listed at the end of this topic.
  5. Fill in the required fields for the authentication provider.
  6. Click Save configuration.

Results

The icon for the third-party authentication provider that you have specified is displayed at the log in screen for the Developer Portal. By clicking on the icon, you are directed to the third-party authentication provider and are requested to enter your authentication credentials. After you enter and submit the authentication credentials, you are redirected back to your Developer Portal site.