Settings
You read every configuration value with the key that sets it, compose a config change to paste into your deployment, keep the attestation registry, mint and revoke admin API tokens, and rotate the client assertion key.
- Who
- Admin
- Where
- Console
In short
Settings shows every configuration value with the key that sets it and changes none of them: its sheet composes a change for you to deploy. It keeps the attestation registry, mints and revokes admin API tokens, and rotates the key agents sign in with, in the order that keeps Entra working.
On this page
Settings has four tabs: Configuration, Attestation registry, API tokens and Agent signing keys. The first two need the config area, the third needs the tokens area, and Agent signing keys needs a full administrator. A tab your session cannot open is named in a line at the top instead. Your configuration itself lives in the config file, the environment or the chart, never in a browser, and this page shows what that means for each tab.
Before you start
- A console sign-in that holds the
configarea, thetokensarea, or both. - Access to the config file or the chart values of your deployment, for any change you decide to make.
Read the configuration
- Settings
- Configuration
The Configuration tab, with each setting’s key, its environment variable, its value and the badge relaxed. Show the whole screenThe tab opens with
Read from the config file, the environment and your chart, never from the database. Nothing here changes in a browser; each row says where to set it.Rows sit in six groups: Deployment, Sign-in, Governance, Approvals, MCP servers and Recording. Each row shows its name, the key and the environment variable that set it, such asgovernance.minAttestation · STRAZA_MIN_ATTESTATION, and the value the server runs with. A value that loosens the server carries the badgerelaxed. Select a name to read what the setting means and its allowed values, and use the copy button to copy the line for the config file.At the foot, Console access lists each Straza role with its holders and the admin areas it opens, such as
straza-adminwithevery area. The map comes fromadmin.roleAreas, which only the config file sets.Compose a config change
- Settings
- Write a config change
The sheet writes nothing. Pick a row in Pick a setting to change and give the new value, and the sheet shows what the change costs, in the row’s own words. The fragment shows the same change three ways: for
straza.yaml, for the chart’svalues.yaml, and as environment variables where they exist. Press Copy the fragment and merge it into your deployment.Deploy it the way your deployment changes config: a restart, a rollout or a chart upgrade. Overview shows the new posture at its next read. Hardening lists the settings worth tightening before production.
Keep the attestation registry
- Settings
- Attestation registry
The registry under the standalone default, with the strip Managed installation is not required.and the hashes ofhooks.claude-code. Show the whole screenThe registry holds the hashes of the hook configurations a managed install writes, grouped by harness:
hooks.claude-code,hooks.codexandhooks.gemini, each with the Linux path of its file, such as/etc/claude-code/managed-settings.json. Each hash lists its platforms and its status.currentis the configuration this server generates for that harness and platform, andallowedis another accepted one, such as an earlier version. The server registers the configurations it generates when it starts.A strip at the top says how strict check-in is. Under the standalone default it reads
Managed installation is not required., becausegovernance.minAttestationisnoneand check-in does not ask for these hashes. Once that setting ismanaged, a client must present a hash this registry accepts.Retire this hash removes one. The question says
A managed box presenting this hash is refused at its next check-in., so retire a hash only after every machine that presents it has a newer configuration.CLI onlystrazactl attestation addregisters a custom configuration, andstrazactl attestation listprints the entries.Enroll a machine explains the attestation levels a machine reports.
Mint an admin API token
- Settings
- API tokens
- New API token
The New API token sheet, with Name, Lifetime and the six cards of The job. Show the whole screen The sheet opens with
A token lets a script or a program call the admin API, such as an IGA connector, a CI job, or one strazactl call from your terminal. Straza never uses it itself.The token is limited to the scopes you give it. Name it for who holds it, because the name shows in the list and in audit records. Pick a Lifetime:expires in 1 day,expires in 7 days,expires in 30 days,expires in 90 days, which is the default,expires in 1 yearornever expires. The hint under the list saysFor one call from your terminal, pick 1 day.Then pick The job. Each card carries the scopes that job needs, each with its reason, and you can remove any of them.
Job What it is for IGA connector midPoint or SailPoint: writes users and role membership over SCIM, reads servers, roles and the change feed. Audit automation Scripts and SIEM-side checks that read the ledger and session state. Policy CI pipeline A pipeline that applies and activates policy sets from a repository. Read-only reviewer An auditor’s evidence pass. Includes transcript content, marked as such. Full root Every admin route, including minting more tokens. Rare on purpose. Custom Build the scopes by hand from the area table. Under Custom, the area table has the columns Area and what it covers and Access. Each row names an area with what it covers under its name, and offers
none,readorread and write. The line under the table saysWrite includes read here: each area offers none, read, or read and write.The scopes then show as the one string that
strazactl api-token create --scopetakes. Press Mint token.Copy the token now
The token is shown once, on the sheet that follows. Only its SHA-256 is stored, so a lost token cannot be recovered. Revoke it and mint another.
CLI onlystrazactl api-token createtakes any duration in--ttl, and a token minted without it never expires. The console offers the fixed lifetimes above.midPoint and Generic SCIM say which scopes each connector needs.
Revoke a token
- Settings
- API tokens
- Revoke
- Revoke token
The question names what the caller loses, such as
Whatever signs in as idm-scim loses the SCIM plane within seconds.Revocation reaches every strazad replica as an event. A call in flight finishes, and the next one is refused with the reason, so mint the replacement first when that caller matters.Rotate the client assertion key
- Settings
- Agent signing keys
- Rotate key
- Create new key
The client assertion key signs the sign-ins of agents that use client credentials at Keycloak, Okta or Microsoft Entra. Keycloak and Okta read a new key from Straza’s key address by themselves. Entra takes only a certificate uploaded to the agent blueprint, so the certificate and every Entra step show only when a provider in the config names a blueprint under
clientCredentials.entraBlueprint. The tab lists the live keys with their status,staged,activeorretiring, the time each was created and, with Entra, the date its certificate ends. Retired keys fold under one line.Rotate key stages a new key, and a panel then walks the rotation in the order that keeps Entra working:
- The new key is published and signs nothing yet. The active key keeps signing.
- With Entra, Download certificate saves the key’s certificate as a
.pemfile, and an Agent ID Administrator uploads it under Credentials, Certificates of the blueprint the panel names by its client id. The panel shows the certificate’s SHA-1 thumbprint the way Entra lists it, so the upload can be checked against Entra’s row. - Promote turns on a minute after staging, once every replica publishes the key. With Entra, it asks you to confirm that the blueprint lists the thumbprint, because Entra refuses every agent until the blueprint holds the certificate.
After the promote, the previous key retires by itself within 2 minutes. With Entra, the panel then reminds you to remove the old certificate from the blueprint, because Entra accepts it until you do, and to link each agent to its Entra agent identity. With no key yet, the head button reads Create key and the same panel follows.
Retire on a row is for a key that may have been copied. Retiring the active key stops every agent sign-in at Keycloak, Okta and Entra until you rotate and promote a new key. Keys, certificates and tokens explains the key and its certificate.
CLI onlystrazactl signing-keys rotate client_assertion,strazactl signing-keys certificate client_assertion <kid>andstrazactl signing-keys promote client_assertion <kid>run the same three steps.
Next
- Delegated administration sets the
admin.roleAreasmap that Console access reads. - Overview and Audit shows the same relaxed settings under Security configuration.
Walked on v1.1.0-117-g106081a8 on 2026-10-06, except minting a token and retiring a hash, which were not done.
A throwaway standalone server on Linux, read as the admin in headless Chromium. The New API token sheet and the config change sheet were opened and closed, and no token was minted and no hash retired. Console screenshots show strazad v1.0.0-1753-ga27c516c, standalone.