{
  "query" : "CREATE TABLE `m7_identity_token_cache` (\\n    `id` BINARY(16) NOT NULL,\\n    `namespace` VARCHAR(64) NOT NULL,\\n    `cache_key` BINARY(32) NOT NULL,\\n    `value` LONGBLOB NULL,\\n    `created` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,\\n    `modified` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,\\n    `expires` DATETIME NULL DEFAULT NULL,\\n    PRIMARY KEY (`id`),\\n    UNIQUE KEY `uq_m7_identity_token_cache_namespace_key` (`namespace`, `cache_key`),\\n    KEY `idx_m7_identity_token_cache_expires` (`expires`)\\n) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci",
  "limit" : null,
  "result" : null,
  "live" : true,
  "error" : "CREATE command denied to user 'm7www'@'localhost' for table `www_m7`.`m7_identity_token_cache`",
  "exc" : **object**
}
M7

M7 Identity

Development access Identity platform and SDKs available for development

Identity security that lasts beyond login.

M7 Identity is an OAuth-adjacent, security-focused CIAM platform. It supports familiar OAuth 2.0 and OpenID Connect flows, then adds M7-aware controls for renewable sessions, token handoff, and boundary validation.

Security target Identity security model

Push software-only identity as far as practical.

M7 keeps familiar authorization flows while strengthening what happens across long-running sessions and connected applications.

  1. 01 Authenticate Begin with familiar OAuth and OpenID Connect shaped flows.
  2. 02 Continue Carry renewable human authority through long-running sessions.
  3. 03 Confirm Use ACK to control when a replacement refresh credential becomes active.
  4. 04 Validate Apply the supported identity contract at the application and service boundaries.
Product aim Strong practical identity security without turning every application team into an identity engineering team

02 / Integration and continuity

Back to top

SDK integration

Advanced identity, packaged for application teams.

Frontend and backend SDKs provide a supported path for B2B and B2C applications. M7's ACK lifecycle protects refresh-token handoff, so an interrupted connection does not force the client to promote a replacement token it never safely received.

01 Frontend

Connect the sign-in experience.

Use the frontend SDK for the browser-facing login and renewable-session path.

02 Backend

Validate the supported identity contract.

Use the backend SDK for tokens, principals, sessions, and protected service boundaries.

03 ACK

Keep interrupted handoffs recoverable.

A successor can remain pending until the client confirms the transition instead of blindly replacing the last usable state.

03 / SSO and visibility

Back to top

Connected identity

One sign-on. One place to understand your users.

Give users a consistent sign-on across connected applications while M7 handles the identity and session-security layer. See who is signed in, monitor session activity, and track usage without rebuilding identity infrastructure inside every product.

01 SSO

Connect applications around one identity.

Users move between participating products without every application inventing its own sign-in system.

02 Visibility

Understand active sessions.

Track signed-in users and session activity from a shared identity surface.

03 Focus

Keep product code about the product.

Let M7 carry the identity-security layer while each application retains its own business authorization.