OAuth 2.0
In the OAuth 2.0 panel of the Configuration tab, you can specify additional connection information that is required when the Authentication Type is 'OAuth 2.0'. We support the OAuth 2.0 SAML bearer assertion flow to request an OAuth access token.
| Field | Visual Diff | Module Property | Description |
|---|---|---|---|
| Keystore Type | Yes | No | The type of keystore being used.
Note: Required if 'OAuth 2.0' is selected for Authentication Type.
Note: JKS, JCEKS, and PKCS#12 keystore types are supported.
|
| Keystore URL | Yes | Yes | The location of the keystore file.
Note: Required if 'OAuth 2.0' is selected for Authentication Type.
Note: When doing configuration for the cloud environment, you must store the keystore file in the workspace and use relative paths when specifying the keystore URL.
|
| Keystore Password | Yes | Yes | The password used when creating the keystore file.
Note: Required if 'OAuth 2.0' is selected for Authentication Type.
|
| Key Alias Name | Yes | Yes | The key alias name.
Note: Required if 'OAuth 2.0' is selected for Authentication Type.
|
| Retry Refresh Token Attempts | Yes | Yes | Use this field to specify the number of times that you tried to refresh the token. |
Note: In terms of Public Cloud, the scope parameter is omitted and the predefined default values are used by AS ABAP internally, OAuth 2.0 with multiple scopes, works as long as the corresponding business roles are added for the business user.
Note: In terms of On-premise/Private Cloud, if the scope parameter is omitted then the request fails. To use the OAuth 2.0 with multiple scopes, you must enter the scopes delimited by space.