DEVELOPER GUIDE
Use environment-specific, least-privilege credentials through an approved flow.
Anabhix user applications use OpenID Connect through configured identity realms. Service or partner integration credentials require separate approval and scope.
Before you begin
- Approved integration
- Assigned environment
- Named credential owner and rotation process
Choose the correct identity flow
Interactive browser users authenticate through the configured OpenID Connect client. Automated integrations must use only the flow and client issued for that integration; they must not automate a human account.
Protect credentials and tokens
Keep secrets out of source control, URLs, logs, screenshots, support messages, and browser storage not designed for the flow. Validate issuer, audience, expiry, scope, and transport requirements.
Handle expiry and denial
Refresh or reacquire credentials only through the approved mechanism. Treat authorization denial as a policy result, not a reason to retry with broader or copied credentials.
Scope and limitations
- Client identifiers, endpoints, scopes, and credential procedures are environment-specific and intentionally omitted from public content.