Auth Service Operations
Auth Service issues usually appear as sign-in failures, authorization failures, missing membership, API key problems, service-account failures, or signing failures.
First Checks
Section titled “First Checks”- Confirm Auth Service is running and ready.
- Confirm it can reach the configured identity provider.
- Confirm platform services are configured to trust the same Auth Service.
- Confirm the user or integration has the expected membership and role.
- Confirm key-management access is available when signing workflows fail.
Common Symptoms
Section titled “Common Symptoms”- User can sign in but cannot open a project: check project membership.
- User cannot perform an action: check role permissions for the current project.
- API key fails: check whether the key was revoked, rotated, or scoped differently than expected.
- Service account fails: check operator-managed service-account configuration and secrets.
- Token exchange fails: confirm the deployment uses Keycloak or Microsoft Entra.
Escalation Information
Section titled “Escalation Information”When escalating, include provider mode, affected user or service account, approximate time, impacted project, and the action that failed. Do not include raw tokens, API keys, or private key material.