Auth Service Operations
Auth Service health depends on database connectivity, identity-provider configuration, key-management access, and correct platform secrets.
Health
Section titled “Health”Use Kubernetes readiness and liveness state as the primary operational signal. If readiness fails, inspect logs for database, IDP discovery, token issuer, or key-management errors.
Identity Provider Issues
Section titled “Identity Provider Issues”Common causes include issuer mismatch, invalid client credentials, missing redirect URIs, missing management API permissions, and disabled user-management settings.
API Key Issues
Section titled “API Key Issues”API key failures usually indicate revocation, expiration, missing scopes, IP restriction mismatches, or use against a route that does not allow API-key authentication.
Service Account Issues
Section titled “Service Account Issues”Worker token failures usually indicate missing service-account credentials, failed bootstrap, mismatched API secrets, or missing DID key reconciliation. For Auth0 and Entra, confirm the worker client ID and secret are set. For Keycloak, confirm either the worker client secret is set or Auth Service has permission to provision the client during bootstrap.