Update Keystore

Overview

Updates an existing keystore and deploys it to environments. Can optionally update referenced JWKs when the keystore is updated.

Endpoint

PUT /apiops/projects/{projectName}/keystores/{keystoreName}/

Authentication

Requires a Personal API Access Token.

Authorization: Bearer YOUR_TOKEN

Request

Headers

Header Value Required
Authorization Bearer {token} Yes
Content-Type application/json Yes

Path Parameters

Parameter Type Required Description
projectName string Yes Project name
keystoreName string Yes Name of the keystore to update

Query Parameters

Parameter Type Required Description
updateReferencedJwks boolean No Whether to update referenced JWKs (default: false)
updateScope string No Scope for updating JWKs: SAME_PROJECT or ALL_PROJECTS (required if updateReferencedJwks is true)

Request Body

The request body should contain the complete updated Keystore object.

Response

Same as Create Keystore response format.

cURL Example

curl -X PUT \
  "https://demo.apinizer.com/apiops/projects/MyProject/keystores/my-keystore/?updateReferencedJwks=true&updateScope=SAME_PROJECT" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "updated-keystore",
    "description": "Updated keystore",
    "keyStoreEnvironmentList": [...]
  }'

Notes and Warnings

  • Referenced JWKs:
    • If updateReferencedJwks=true, JWKs created from this keystore will be updated
    • updateScope determines which JWKs to update: SAME_PROJECT or ALL_PROJECTS
  • Automatic Deployment:
    • Keystore is automatically deployed after update
  • Permissions:
    • Requires ROLE_API_SECURITY permission
    • Requires ROLE_DEPLOY_UNDEPLOY_PROXIES permission for deployment