The OAuth configuration is a simple setup that will allow your users to use an OAuth profiler to authenticate with dashboards. This method is available starting with 10.3.
From the Admin panel select the system dropdown and select Authentication. The screen should look like the following image.
There are several fields that need to be populated and they will be unique to the provider:
Identity Providers Name: A text field and show the text at the end of "Login with ______".
Authorization Endpoint: Endpoint on the authorization server where the resource owner logs in, and grants authorization to the client application
Token Endpoint: HTTP endpoint that micropub clients can use to obtain an access token given an authorization code.
UserInfo Endpoint: Uses the access token rather than the ID token to look up the user info.
UserInfo Mapping Claims: information that is requested from the authorization account to be returned to dashboards. Sub is required, email would be another common request. For additional information on claims, you can see the following documentation OpenID Claims 5.1.
To Obtain the Client ID and Client Secret you will need to obtain that information directly from the authorization source.
To configure Google as your authorizer you will need to use the Google Developers Console.
Select the Credentials section and you can choose to use an existing OAuth 2.0 Client IDs or create a new Client ID by click Create Credentials at the top of the page. You will need to select the OAuth Client ID and will be prompted for the application type. We will be using Web Application.
If you do not have a fully qualified domain name you will need to perform this next setup thought localhost until you have your domain.
Once you have populated the callback URL you are able to press the Create button.
The next screen is where you will be able to get the Client ID and Clent Secret.
Last you will need to check the enable button.