Field | Description |
Name | Name of a third-party provider. For example, Amazon. You can also use one of the following pre-configured third-party providers that is shipped with the API Gateway installation: ![]() ![]() Note: Considerations while using the PingFederate providers: ![]() ![]() |
Client metadata field mapping. Specifies the mapping of dynamic client registration specification to that of the client implementation of the provider. The Client metadata field mapping fields are required when you are adding a third-party provider that is not shipped with API Gateway. | |
Specification name | The client metadata attributes in accordance with the dynamic client registration specification as defined in RFC 7591. The available values are: ![]() Note: If you do not specify this attribute, API Gateway automatically generates the URL. ![]() ![]() ![]() ![]() ![]() ![]() ![]() Note: The logo_uri is currently not supported in API Gateway. ![]() Note: If you do not specify this attribute, the authorization server registers the client with a default set of scopes. ![]() ![]() Note: The tos_uri is currently not supported in API Gateway. ![]() Note: The jwks_uri is currently not supported in API Gateway. ![]() ![]() |
Implementation name | The client metadata attributes that are used by the authorization server, but are not in accordance with the dynamic client registration specification. Example: ![]() ![]() ![]() ![]() ![]() ![]() |
Extended request parameters. Specifies the additional client metadata attributes that are specific to the authorization server, and are not specified in the dynamic client registration specification. In PingFederate (For example): forceSecretChange = true | |
Type | Specifies the client metadata attribute type. The available values are: Client read, Client registration, Client update, Client delete. |
Key | The client metadata attribute key that is specific to the authorization server. |
Value | A value for the client metadata attribute key. When sending requests to the authorization server, this value is appended to all requests. You can add multiple request parameters by clicking + Add. |
Application profile. Specifies the application profile that is specific to the authorization server. | |
Type | Specifies custom application type other than web and native. By default, the web and native application is added. You can add multiple application type by clicking + Add. You can also modify and delete the added application type by clicking the respective Edit or Delete icon. |