OmniAuth Console

OmniAuth Console

One console for tenants, apps, customer organizations, and integration readiness.

Set up hosted identity, create OIDC applications, generate non-secret integration metadata, and manage B2B2C customer access from one product surface.

Start in OmniAuth Console

Create an account, set up the tenant and app, then validate login and field integration from the console.

  1. 1. Create account
    Start with hosted signup for the console identity.
  2. 2. Create tenant
    Create or select the tenant/customer that owns policy and apps.
  3. 3. Create app
    Create the OIDC application for the field or product environment.
  4. 4. Choose app type
    Choose web, SPA, or service app defaults before generating config.
  5. 5. Configure redirects
    Set callback and logout URLs for the selected environment.
  6. 6. Issue credentials
    Create credentials safely and keep one-time values out of durable surfaces.
  7. 7. Invite admins/users
    Invite tenant admins, customer organization admins, or users with scoped roles.
  8. 8. Test login
    Run hosted login and return to the console setup flow.
  9. 9. Integration status
    Review the integration snippet, field packet, and readiness checks.

Hosted identity

Signup and signin route through the configured identity provider.

App integration

OIDC issuer, discovery, JWKS, and auth-api metadata stay copy-safe.

B2B2C control

Tenant-owned customer organizations and delegated roles live in the console.

Use console first

OmniAuth Console is the human product surface. Use it for setup, field onboarding, B2B2C access, and operator readiness; the other public URLs are service endpoints behind the flow.

OmniAuth Console

Service endpoints

IdP
OIDC issuer and discovery endpoint opened by console sign-in and generated config.
https://idp.dev.verity.gridfx.io/
SSO
Hosted login routing endpoint launched from console test-login flows.
https://sso.dev.verity.gridfx.io/
Auth API
Health and token-exchange API endpoint represented through readiness checks.
https://auth.dev.verity.gridfx.io/healthz
Team
Reference app surface for validation, not the primary setup destination.
https://team.dev.verity.gridfx.io/