Set Client Polaris Credentials
Changed onPersist an externally-obtained Polaris client_id/secret pair.
Use when the Polaris principal already exists with credentials CAMS didn't mint (e.g. created by a non-internal-token flow), so the normal mint/rotate path is unavailable. The operator pastes the existing pair — sourced from the customer's vault, the original onboarding ticket, etc. — and CAMS stores them so the SQL editor's "Connect Your Query Engine" modal can surface them like any other client.
Does not call Polaris and does not validate the pair against Polaris. If the values are wrong, the customer's SQL editor sessions will 401 when they try to use them.
All three columns (principal_name, client_id, client_secret) are required on the request and written together — the row never carries client_id/secret without a principal_name.
Request
- Base URL: https://carbonarc.ai (the document declares no server; this is the origin it was published from)
- URL: https://carbonarc.ai/api/v1/admin/polaris/clients/{client_id}/credentials
- Auth: OAuth 2 (authorization code, authorization URL authorize, token URL token)
Path parameters
Request body
Response
Successful Response
Changes
- breaking
added the pattern
^[a-zA-Z0-9_-]+$to the request property - warning
the
request property's maxLength was set to128
- breaking