Endpoint
Authentication
Requires a Personal API Access Token.Header
Request
Headers
| Header | Value | Required |
|---|---|---|
| Authorization | Bearer | Yes |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
| username | string | Yes | Username of the credential |
| jwkName | string | Yes | Name of the JWK to assign for decryption and encryption |
Notes
- JWK must exist in the project or in the admin project
- Credential must exist
- Only one JWK can be assigned for decryption and encryption at a time
- Assigning a new JWK replaces the existing one if present
- JWK is used for JWT decryption and encryption operations
Response
Success Response (200 OK)
Error Response (400 Bad Request)
Error Response (401 Unauthorized)
Error Response (404 Not Found)
cURL Example
Notes and Warnings
-
JWK Requirements:
- JWK must exist in the project or admin project
- JWK name is case-sensitive
-
Credential Requirements:
- Credential must exist
- Credential must be in the same project or accessible from the project
-
Replacement Behavior:
- Assigning a new JWK replaces any existing JWK for decryption and encryption
- Previous JWK assignment is automatically removed
-
Usage:
- JWK is used for JWT decryption operations
- JWK is used for JWT encryption operations
- Separate from JWK used for validation and signing
-
Automatic Deployment:
- Credential is automatically deployed to all environments after JWK assignment
- Deployment results are returned in the response
Permissions
- User must have
IDENTITY+MANAGEpermission in the project - For automatic deployment, user must also have
IDENTITY+DEPLOY_UNDEPLOYpermission
Related Documentation
- Remove JWK Encryption - Remove JWK for decryption and encryption
- Set JWK Validation - Assign JWK for validation and signing
- List Credentials - List all credentials

