Mockoon Pro supports three authentication modes:
Public registration is closed; new users join through single-use invitation links or enterprise SSO.

In local authentication mode, user accounts and credentials are saved in your local database. Users sign in at /login with their email and password, and the team owner can generate invitation links from the Users (/users) page. This mode operates completely offline without external identity provider dependencies.
The Users page (/users) allows the team Owner to oversee team access:
User to Owner) using the role selector. You cannot change your own role, and the last remaining Owner can never be demoted. The roles of disabled users cannot be changed.
For local accounts, invitations are the primary method for adding new team members.
💡Invitations are only applicable for local accounts and do not apply to users logging in via OIDC SSO.
/users).User or Owner).https://mockoon.company.com/invite?token=...).💡 Invitation links are valid for 7 days and expire automatically if unclaimed.
OIDC Single Sign-On delegates authentication to your Identity Provider (IdP) for centralized user lifecycle management, MFA, and access control.
Supported identity providers include Microsoft Entra ID, Okta, Keycloak, Google Workspace, Auth0, Ping Identity, and any provider supporting OpenID Connect Discovery (.well-known/openid-configuration).
mockoon.company.com with your own domain):
Copyhttps://mockoon.company.com/auth/oidc/callback
/settings).https://login.microsoftonline.com/<tenant-id>/v2.0 or https://auth.company.com/realms/mockoon).
Settings are verified and applied immediately without restarting the server.
Mixed mode enables Local database and OIDC Single Sign-On together. It is useful when progressively adopting SSO or when selected users and administrators still require local password access.
Authentication is determined per account. Local accounts continue to use their email address and password, while OIDC accounts authenticate through the configured Identity Provider.
When an existing local user (such as the initial administrator) signs in through OIDC with a verified email matching their local account, Mockoon automatically links the accounts while preserving the user's team role, workspace access, and environments.
After an account is linked, OIDC supersedes local password authentication for that account. The stored password is removed, existing sessions are revoked, and the user must subsequently sign in through the Identity Provider. Other unlinked local accounts can continue using password authentication while mixed mode is enabled.
Restrict invitations and logins to approved corporate email domains:
/settings).company.com, engineering.company.com).When set:
Leave empty to allow all email domains.
