Identity continuity
Keep a defined sign-in path when a provider is unavailable.
Authonomy connects an application to another approved provider when that path satisfies the same identity contract. When no approved path can do that, sign-in is denied.
Continuity boundary
The alternate path meets the application’s requirements.
Each governed application has an identity contract: who can authenticate, what assurance is required, and which claims the application expects. An alternate provider path is usable only when it can satisfy that contract.
The provider continues to run its own login and remains authoritative for the identities it holds. Authonomy validates the result and supplies the application-facing identity in the form the application already uses.
When no approved route satisfies the contract, Authonomy denies sign-in. It does not create a substitute identity or lower the application’s assurance requirements.
What this depends on
Authonomy’s own services remain part of the sign-in path.
Identity continuity requires Authonomy’s own services to be available. When they are unavailable, new sign-in stops. There is no offline authentication mode.
Scope the path
Continuity is an application decision.
The provider paths, claims, assurance, and denial behavior are agreed for each application. That keeps the continuity decision explicit and reviewable by the teams responsible for the application and the identity estate.
Choose an application where continuity matters.
We’ll define its identity contract, provider paths, dependencies, and safe denial behavior.