Skip to content
InovagioInovagio

AuthIdentity and sign-in

One sign-in for every person, service and AI agent.

Works with the identity provider you already run, and gives every agent its own scoped, expiring credential.

We’ll spend 30 minutes with you on one of your workflows, and you don’t need to share any data.

IT’s task in the Inovagio App: confirm sign-in works through the company’s directory, with a user outside the department seeing nothing.

Where Auth works

One sign-in for people, services and Virtual Employees (Auth). These are the onboarding steps it works in, from your first decision to live work.

  1. Step 0 · AccountOpen your accountRemoves: The open-ended vendor login.
  2. Step 2 · Set upSet up sign-in and accessRemoves: AI on a shared or borrowed login.

How the ten steps work

What Auth does

Auth is Inovagio’s identity server: it signs in people, services and AI agents over OpenID Connect and OAuth 2.0, federates to the identity provider you already run, and issues the tokens every Inovagio service trusts.

  • Standards-based sign-in

    OpenID Connect discovery, authorization code with PKCE (S256 only), client credentials, refresh and token exchange, with the implicit and password grants left out by design.

  • Refresh-token theft detection

    Refresh tokens rotate on every use; replaying a retired one revokes its whole family and raises a critical audit event.

  • Your identity provider, federated

    People sign in through enterprise identity providers over OIDC or SAML 2.0, while Inovagio stays the one issuer and the one point of revocation.

  • Multi-factor and passkeys

    TOTP with recovery codes, step-up authentication and passkeys, mandatory for platform administrators.

  • Agents act for a person

    Signed, scoped, expiring delegation grants let the audit trail say which person an agent acted for, and within which grant.

  • Device sign-in for terminals

    The CLI signs in with the device authorization grant, and that session authorizes its requests.

  • Keys you can rotate and protect

    Signing keys move through pending, active, retiring and retired stages with overlap validation, held in an OS keystore, KMS or HSM in server deployments.

  • Provisioning and offboarding

    SCIM 2.0 creates, updates and removes accounts and groups from your directory, and deactivation revokes access in the same request.

  • Every decision audited

    Each sign-in, token issue and admin change is written to the platform’s tamper-evident audit trail, which cannot be turned off.

Auth at work

In the App at step 2: Set up sign-in and access.

  • Groups mapped to roles: 14 people see Finance.
  • A second account signs in: passed.
  • A user outside Finance sees nothing: passed.
The Inovagio App at step 2 for the example company Harlow Distribution: the IT administrator confirms that sign-in works through the company’s directory, with groups mapped to roles, a second account signing in, and a user outside Finance seeing nothing, each test passed.
Sign-in through your company’s directory, tested with a second account and a user who must see nothing.

Inside Auth

The views Auth gives the people who run it, on sample data from Inovagio’s example companies.

The Set up step in the Inovagio App for Keelstone Aerospace, an example company with example data. It shows the sign-in tests run through the company’s own directory: a second account signs in, a user outside the department sees nothing, a forged account is refused, and a Virtual Employee starts with no access.

Auth › Sign-in: the sign-in tests run through the company’s own directory: a second account signs in, a user outside the department sees nothing, a forged account is refused, and a Virtual Employee starts with no access. Sample data from Inovagio’s example companies.

Everything Auth does, by area.

Protocols

  • OIDC discovery and JWKS
  • Authorization code with PKCE (S256 only)
  • Client credentials with per-client grant control
  • Refresh-token rotation with reuse detection
  • Token exchange (RFC 8693)
  • Device authorization grant (RFC 8628)
  • Token introspection and revocation
  • RP-initiated logout

Sign-in methods

  • Passwords hashed with Argon2id
  • TOTP with recovery codes and step-up
  • Passkeys (WebAuthn registration and assertion)
  • Magic links
  • Social sign-in providers
  • Enterprise OIDC federation
  • SAML 2.0 federation with full assertion validation

Administration

  • Tenant, user and application administration
  • Role-based access with a fine-grained permission catalog
  • No principal can administer a more privileged one
  • OAuth consent screens
  • Per-tenant branding of hosted sign-in pages
  • SCIM 2.0 users, groups, filtering, PATCH and bulk
  • Self-service signup and account recovery without user enumeration

Tokens and keys

  • EdDSA (Ed25519), RS256 and ES256 signing, chosen per client
  • Key rotation with overlap validation
  • Tiered key custody: local, OS keystore, KMS or HSM
  • Complete ID-token claims (at_hash, auth_time, azp)
  • Discovery lists only what the server supports

What Auth replaces

Auth does the work of these, inside one platform with one identity, one policy and one record:

  • Separate identity provider for internal apps
  • Per-application user stores
  • Shared admin passwords and static API secrets
  • Manual account provisioning and offboarding

The controls Auth brings

Every Inovagio product keeps the same five commitments, because regulated work needs all five at once.

  • Security

    Sign-in through your identity provider, with tokens signed and short-lived.

  • Governance

    Roles and permissions for people, services and agents in one model.

  • On the record

    Every sign-in, grant and change is recorded.

  • Monitoring

    Sign-in activity and failures appear in Panoptes.

  • Cost per task

    One identity service for every product, with no per-user charge.

Auth in your industry

Every industry runs the same ten steps, so Auth does the same job in each, on that industry’s own work.

For developers: Auth at a glance

Standards
OpenID Connect, OAuth 2.0 with PKCE (RFC 7636), token exchange (RFC 8693), device grant (RFC 8628), SAML 2.0, SCIM 2.0 (RFC 7643/7644), WebAuthn
Grants left out
Implicit and resource-owner password, as OAuth 2.1 recommends
Signing algorithms
EdDSA (Ed25519), RS256, ES256
Password hashing
Argon2id
Conformance
Built to the OpenID Foundation Basic OP and Config OP profiles
Identity store
MNEMOS, event-sourced
Platforms
macOS, Linux and Windows servers

Request the developer editionSee the architecture

Auth in the platform.

Where Auth fits

One platform
  1. Agent HarnessAgent harness

    Inovagio CLIInovagio DesktopWeb ChatInovagio SDK

  2. OpsisExperience layer

    FolioMorphe

  3. Virtual EmployeesVirtual Employee layer

    NexusErgon

  4. SynesisKnowledge layer

    PerceptionMNEMOS

  5. OriginModel layer

    Inference ServerForge

  6. Phylax (this layer)Trust layer

    Auth (this product)Inovagio SecretsGuard

  7. OperationsOperations

    PanoptesArchon

  8. Platform servicesPlatform services

    ServerAPI ManagementConnect

Where Auth fits

Further reading

Guides and posts on Auth

See Auth on one of your workflows.

Every project starts with one workflow your people know well, measured against what it costs you today.