RapidIdentity Product Guide: Legacy UI

OAuth2 Credentials

Currently, the RapidIdentity Connect OAuth2 Credentials tab allows administrators to add Google, Google Extended (i.e. Service Accounts), and Edmodo OAuth 2.0 credentials.

Read Configuring OAuth2 for G-Suite Adapter for specific information on Google OAuth2 configuration.

Legacy_OAuth2_G-Suite.png

Administrators can select any existing project, or select the asterisk to make the credential available across all existing projects.

Upon selecting the appropriate project and clicking Add, selecting Google or Edmodo opens a specific Request OAuth Credential window.

Legacy_Oauth2_Add_Credential.png
Legacy_Oauth2_Add_Permission.png

The Add Custom Permission button allows administrators to specify additional scopes to authorize when the desired scope is not listed. This allows administrators to make API calls that are not supported by RapidIdentity Connect directly.

Edmodo's login mechanism, Edmodo Connect, and Google APIs both employ the OAuth 2.0 protocol to authenticate and authorize, and RapidIdentity Connect supports both.

Since an Edmodo account automatically includes OAuth 2.0 through login, simply enter the Name (to reference the eventual RapidIdentity Connect Action for Edmodo OAuth, i.e. (EdmodoOAuth) and the corresponding Edmodo username.

RapidIdentity Connect's and Google's UI have both changed slightly since the video was first produced, however, the overall sequence to request and employ the OAuth credential remains the same.

Once the request is complete the grid interface will display the credential.

To remove the credential, click the checkbox and then click Delete (administrators should also go to the Google Developers Console to delete the Client ID as well).