API Key Authentication
API keys are the recommended method for server-to-server integrations, CI/CD pipelines, and SDK usage. Pass the key in theAuthorization header:
Session Authentication
Session-based auth is used by the Studio and browser clients. It requires a CSRF token for all mutation requests.Login
Example request:mdcms_session HTTP-only cookie and a mdcms_csrf cookie containing the CSRF token. Include the CSRF token in the X-MDCMS-CSRF-Token header for all subsequent mutation requests.
Logout
Example request:SSO Authentication
Initiate OIDC
Example request:redirectUrl. After successful authentication, the provider redirects back to the MDCMS callback URL, which establishes a session.
SAML Assertion Consumer
SAML assertion consumer service endpoint. Receives and processes SAML
assertions from the identity provider after authentication.
SAML Metadata
Returns the SAML service provider metadata XML document. Use this URL when
configuring MDCMS as a service provider in your identity provider’s admin
console.
Content-Type: application/xml.
CLI Device Flow
The CLI uses a device authorization flow to authenticate without exposing credentials on the command line. This flow is initiated bymdcms login.
Start Challenge
Begin a CLI device authorization flow. Returns a challenge ID and a URL for
the user to authorize in their browser.
Authorize Challenge
Authorize a pending CLI device challenge. Called from the browser after the
user logs in and approves the CLI session.
Exchange Code
Exchange the authorization code for an API key. Called by the CLI after the
user authorizes the challenge.
Current Principal
Get Current User
Returns the current authenticated principal’s identity and capabilities within
the active project and environment.
Environments
List Environments
Example request:The
X-MDCMS-Environment header is still required for this endpoint, even
though it returns all environments. The header is used for authentication
context.