Provider registration
Register an HTTPS OIDC issuer, client, secret, and exact callback through a bearer-protected tenant route.
2AYE now implements OIDC discovery, exact issuer and audience validation, state, nonce, PKCE S256, signed ID-token validation, replay prevention, 2AYE session issuance, and audit evidence. Provider-specific certification and SAML are separate interoperability work and are not implied.
Register an HTTPS OIDC issuer, client, secret, and exact callback through a bearer-protected tenant route.
Reject issuer, audience, signature, lifetime, nonce, state, redirect, tenant, and replay failures.
Map the external subject to a tenant-bound workforce principal and issue a 2AYE session and authorization code.
Record provider registration, login start, rejection, and completion without storing raw external subjects in audit data.
Each consequential action moves through the same six control points. See where 2AYE evaluates authority, requests human review, and preserves the outcome.
Your next move
Choose a step.
See what matters for your workflow.
Focus / 01
Connect an application through tenant-bound OIDC login.
Explore the developer guideReview the integration requirements and supporting evidence for this capability. Talk to us