Skip to content

Rotate credentials

Replace the client secret Identiguard uses to connect to Okta or Entra ID. The same steps resume a monitor that has paused itself.

  • The admin role in the workspace. Members and viewers cannot open the Edit page.
  • Admin access to the identity platform, to create the new secret.
  • Any plan.
  1. Create the new secret in the identity platform. Do not delete the old one yet.
    • Okta: open the Identiguard integration in the Okta Admin Console and generate a new client secret.
    • Entra ID: open the app registration, go to Certificates & secrets and create a new client secret. Copy its Value, not the Secret ID. Note its expiry date.
  2. In Identiguard, open Tenants.
  3. In Tenant overview, choose the pencil icon (Edit) on the tenant’s row.
  4. Scroll to the Credentials card. Rotate credentials is the heading of the form inside it.
  5. Paste the new secret into Client Secret.
  6. Leave Client ID (optional) blank to keep the current client ID. Fill it in only if the client ID changed, for example with a new app registration.
  7. Choose Validate & save credentials. The button reads Validating… while Identiguard checks the secret with Okta or Microsoft.
  8. Confirm the alert Verified with “Credentials updated and verified against Okta.” or “Credentials updated and verified against Microsoft.”
  9. Delete the old secret in the identity platform.

Identiguard checks the new credentials with the platform before it saves them. If the check fails, you see the alert Credentials rejected with the reason, the old secret stays in place and monitoring continues as before.

Identiguard pauses an Okta agent monitor or the Entra ID poll after 5 failed checks in a row. See Tenant health. A successful rotation is the only way to resume. There is no separate resume button.

You know a monitor is paused when you see one of these:

  • The toast <tenant name> connection unhealthy.
  • The alert Monitoring paused in the Credentials card.
  • For Okta agents, Status: Paused after repeated failures and a locked checkbox under Agent Monitoring.
  • An email with the subject Monitoring disabled for <tenant name>.

Steps:

  1. Choose Review settings on the toast. Or open Tenants and choose the pencil icon (Edit) on the tenant.
  2. Scroll to the Credentials card and confirm the Monitoring paused alert.
  3. Create a new secret in Okta or Entra ID. If the secret is still valid and the fault was elsewhere, have the current secret to hand.
  4. Enter Client Secret. Enter Client ID (optional) only if it changed.
  5. Choose Validate & save credentials.
  6. Wait for the alert Verified.

Monitoring restarts at once. The Monitoring paused alert goes, the agent checkboxes unlock and the monitor state reads “Credentials updated. Awaiting next check.” until the next check runs.

Identiguard holds no Auth0 credentials. An Auth0 tenant’s Edit page has no Credentials card, and there is nothing to rotate on the Auth0 side.

What exists is up to three tokens that Auth0 uses to send data to Identiguard. Each is shown once when it is created.

Token Can you replace it yourself?
Log stream token No. It cannot be reissued. Delete the tenant and create it again.
Metric stream token No screen exists for this. Contact the product team.
Action logs token No screen exists for this. Contact the product team.

Replace a lost or exposed log stream token

Section titled “Replace a lost or exposed log stream token”
  1. Open Tenants and choose the pencil icon (Edit) on the Auth0 tenant. Note the tenant name, customer name and the ticked types under Event Subscriptions.
  2. Go back to Tenants and delete the tenant with the bin icon (Delete tenant). See Managing tenants.
  3. Under Create a tenant, choose Connect on the Auth0 card and create the tenant again. See Connect Auth0.
  4. Copy the new Endpoint URL and Authorization token (shown once).
  5. In Auth0, edit the existing log stream. Replace the payload URL and the Authorization header value. With Terraform, apply again with the new identiguard.tf and terraform.tfvars values.
  6. If the old tenant had a metric stream or Action logs, set them up again. Their endpoints and tokens are new as well.
  • The alert Verified directly after you save.
  • No <tenant name> connection unhealthy toast after you reload the application.
  • For Okta, under Agent Monitoring, a Status: other than Paused after repeated failures after the next check.
  • For Entra ID, new events after the next poll.

Entra ID secrets have an expiry date. Put a reminder in the service calendar a month before.

All of these appear in the alert Credentials rejected unless noted. When you see it, nothing was saved and the old secret is still stored.

What you see Why What to do
“Client secret is required.” Client Secret is blank Paste the secret.
“Client ID is required.” The Okta tenant has no stored client ID Enter the client ID in Client ID (optional) as well.
“Okta rejected these credentials: authentication failed. Check the client ID and secret.” Okta refused the sign-in, or the integration cannot read agent pools Check the secret and client ID. Check that the integration grants okta.agentPools.read.
“Could not verify these credentials with Okta. Try again shortly.” Okta did not answer Try again in a few minutes.
“Microsoft rejected these credentials: <description>” or “Microsoft rejected these credentials: Credentials rejected” Microsoft refused the sign-in Check that you pasted the secret Value and that it has not expired. If the app registration changed, enter the new client ID too.
“Microsoft tenant configuration is missing the stored client ID; provide a new client ID.” or “Failed to read the stored Microsoft client ID; provide a new client ID.” Identiguard cannot read the stored client ID Enter the client ID in Client ID (optional) as well.
“Microsoft tenant configuration is missing the directory tenant ID; recreate the tenant.” The stored configuration is damaged Delete the tenant and create it again. Escalate to the product team.
“Okta tenant configuration is missing the domain; recreate the tenant.”, “Okta tenant configuration is missing its encryption key; recreate the tenant.” or “Failed to access the Okta tenant encryption key; recreate the tenant.” The stored configuration is damaged Delete the tenant and create it again. Escalate to the product team.
“Identiguard stores no Auth0 credentials. Manage the log stream in the Auth0 dashboard or in your Terraform configuration.” A rotation was sent for an Auth0 tenant Nothing to rotate. See Auth0.
“Forbidden: Insufficient permissions. Admin role required to rotate credentials.” You are not an admin Ask a workspace admin.
The checkbox under Agent Monitoring is still locked The rotation did not succeed, or the page is out of date Check for the Verified alert, then reload the page.
The toast comes back after a successful rotation A different fault, such as a missing permission or licence on one Entra ID stream Read the toast text and see Tenant health.