Rotate DataHub token-service secrets
Changed onGenerates fresh values for DATAHUB_TOKEN_SERVICE_SIGNING_KEY (the key GMS uses to sign API access tokens) and DATAHUB_TOKEN_SERVICE_SALT (the salt behind the token revocation-check hash), updates every DataHub app child that carries them, and triggers a coordinated restart so the new values take effect everywhere simultaneously. USER-VISIBLE SIDE EFFECT: every previously issued API access token (personal access tokens, service tokens) is permanently invalidated. The tokens are stateless JWTs, so the old key and salt cannot be recovered and matching tokens cannot be reissued. Users and automations must create new API tokens through the UI or GraphQL API. Browser sessions (cookie-based) are unaffected.
Request
- Base URLhttps://api.aiven.io/v1
- URLhttps://api.aiven.io/v1/project/{project}/service/{service_name}/rotate-token-service-secrets
- AuthHTTP bearer and OAuth 2Authorization code: https://console.aiven.io/oauth/authorizeToken URL: https://api.aiven.io/v1/oauth2/token scopes: services:write
Path parameters
Project name
Service name
Response
Response
Changes
- info
endpoint added
- info