Additional OAuth 2.0 Authentication Configuration Parameters
Set the following parameters in the Application Debug page when the Authentication Method is set to OAuth 2.0 and the Grant Type is either Client Credentials or Refresh Token.
Note
These additional configurations are optional and not necessary to configure OAuth 2.0 authorization. Refer to OAuth 2.0 Configuration Parameters for additional information on required OAuth 2.0 parameters.
To have customized headers as a part of the access token generation request, add the oauth_headers
parameter as follows:
<entry key="oauth_headers">
<value>
<Map>
<entry key="Content-Type" value="application/x-www-form-urlencoded" />
</Map>
</value>
</entry>
To send additional headers alongside the Authorization header for token generation, add the oauth_headers
parameter as follows:
<entry key="oauth_headers">
<value>
<Map>
<entry key="customHeaderKey" value="customHeaderValue"/>
</Map>
</value>
</entry>
SCIM2 supports exclusion of headers in the OAuth 2.0 header request. The keys for headers to exclude from the OAuth 2.0 header request can be added as comma-separated values in the entry key as follows:
<entry key="oauth_headers">
<value>
<Map>
<entry key="oauth_headers_to_exclude" value="Authorization,CUSTOM_HEADER"/>
</Map>
</value>
</entry>
For some managed systems, additional custom request parameters may be required to be included in the access token generation request. To send additional parameters for token generation, add the following entry with your desired parameters:
<entry key="oauth_request_parameters">
<value>
<Map>
<entry key="customParamKey" value="customParamValue"/>
</Map>
</value>
</entry>
To delete any of the standard request parameters not supported by managed systems access token generation requests, add the following entry with your desired parameters:
<entry key="oauth_body_attrs_to_exclude">
<value>
<Map>
<entry key="oauth_body_attrs_to_exclude"
value="customParamKey1,customParamKey2"/>
</Map>
</value>
</entry>