Dynamic System Settings for OAuth 2.0 authentication

When you configure user authentication with OAuth 2.0 tokens, you must create several Dynamic System Settings to enable authentication.

The following table lists required settings and explains their meaning:

Setting name	Scope	Description
OAuth2/token_endpoint	Pega-AppDefinition	The URL of the OAuth 2.0 server that Pega Mobile Client uses to obtain tokens.
OAuth2/userinfo_url	Pega-AppDefinition	The URL of the OAuth 2.0 server that Pega Platform uses to validate tokens, and to obtain basic information about the user who presents an access token.
OAuth2/client_secret	Pega-AppDefinition	A setting that is used to pass the client_secret credential.
OAuth2/client_id	Pega-AppDefinition	A setting that is used to pass the client_id credential.
OAuth2/scope	Pega-AppDefinition	A setting that lets Pega Mobile Client determine the identity and email address of authenticated users. It must be set to email profile.
OAuth2/grant_type	Pega-AppDefinition	A setting that Pega Mobile Client passes to the authorization server to establish the authorization mode. It must be set to password.
authentication_type	Pega-AppDefinition	A setting that notifies Pega Platform whether to authenticate mobile users based on user credentials or OAuth 2.0 tokens. To use OAuth 2.0 token-based authentication, set the value to oauth2. To use credentials-based authentication, set the value to basic or leave it blank.
authentication/maxLoginAttemptsCount	Pega-Engine	This setting is used for handling OAuth 2.0 server connectivity problems. Set the value to a number of failed attempts to connect to the userinfo endpoint of the OAuth 2.0 server that can occur before Pega Platform returns an internal server error.