M7 Identity

Development access Multi-tenant IdP and SDKs available for development

Identity authority for people, machines, and every tenant.

M7 Identity is a general-purpose identity provider for custom applications, organizations, and federated services. It supports OAuth 2.0 and OpenID Connect for interactive and device flows, explicit machine authentication with client credentials, and M7-aware controls for renewable sessions and credential lifecycle.

Security model Identity authority model

Make every principal and security context explicit.

M7 separates human sign-in from machine authentication, and control-plane users from tenant-member identities, while carrying lifecycle policy through connected systems.

  1. 01 Resolve Determine the human, member, application, service, or device flow and the organization context it belongs to.
  2. 02 Issue Create credentials for the intended client, organization, audience, scope, and principal class.
  3. 03 Renew Continue supported sessions through rotation, binding, and optional ACK-controlled activation.
  4. 04 Close Inspect, revoke, end, or recover supported credentials and session state through explicit lifecycle operations.
Product aim One identity authority for custom systems without treating people, machines, and tenants as the same kind of principal

02 / Human and machine access

Back to top

Application integration

Human and machine access, through one identity platform.

Use authorization code with PKCE for interactive applications, device authorization for constrained clients, and client credentials for service-to-service access. Frontend and backend SDKs carry the supported token, principal, and renewable-session contracts into the application boundary.

01 Human

Connect interactive sign-in.

Use hosted OAuth 2.0 and OpenID Connect flows for browser, server-rendered, SPA, and native applications.

02 Machine

Authenticate services explicitly.

Issue audience- and scope-bound client-credentials tokens without borrowing a user's identity or session.

03 Lifecycle

Keep credentials governable.

Refresh, acknowledge, inspect, revoke, and end supported token and session state through explicit lifecycle operations.

03 / Tenancy and federation

Back to top

Organization identity

Model every tenant as a security context.

Manage organizations, members, groups, OAuth applications, policies, and identity connections without treating every account as the same kind of user. M7 separates control-plane management from tenant-member access and preserves organization context across supported issuance paths.

01 Tenancy

Keep control and member identities distinct.

Users manage organizations through explicit authority while member credentials remain inside their intended tenant context.

02 Policy

Apply tenant-local identity policy.

Configure registration, login groups, token policy, application behavior, and hosted identity settings for each organization.

03 Federation

Connect without flattening identity.

Use OAuth and OpenID Connect discovery, dynamic registration, and federated sign-in while preserving client and organization context.