POST /api/v1/authorizationServers/{authServerId}/resourceservercredentials/keys
Adds a new JSON Web Key to the custom authorization server`s JSON web keys.
Note: This API doesn't allow you to add a key if the existing key doesn't have a
kid. Use the Replace an Authorization Server operation to update the JWKS or Delete a Custom Authorization Server Public JSON Web Key and re-add the key with akid. Note: This API doesn't allow you to add a key with an ACTIVE status. You need to add an INACTIVE key first, and then ACTIVATE the key.
Servers
- https://{yourOktaDomain}
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
authServerId |
String | Yes |
|
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
n |
String | No |
RSA key value (modulus) for key binding |
kty |
String | No |
Cryptographic algorithm family for the certificate's key pair |
e |
String | No |
RSA key value (exponent) for key binding |
kid |
String | No |
Unique identifier of the JSON web key in the custom authorization server's public JWKS |
status |
String | No |
Status of the JSON Web Key Valid values:
|
use |
String | No |
Acceptable use of the JSON Web Key |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.