Handle SAML authentication request (Redirect binding)

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://openapi.logto.io/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json 
{
  "Logto API references MCP server": {
    "url": "https://openapi.logto.io/mcp"
  }
}
Close
GET /api/saml/{id}/authn
O auth2

Process SAML authentication request using HTTP Redirect binding. The application policy or ForceAuthn can require fresh authentication; otherwise an existing session may be reused. The response assertion preserves the actual authentication time. When authnRequestConfig.requireSignedAuthnRequests is true, the request must be signed using the configured service provider signing certificate.

Path parameters

  • id string Required

    The ID of the SAML application.

Query parameters

  • SAMLRequest string Required

    The SAML request message.

    Minimum length is 1.

  • Signature string

    The signature of the request.

  • SigAlg string

    The signature algorithm.

  • RelayState string | null

    The relay state parameter.

    Maximum length is 512.

Responses

  • 200 application/json

    OK

  • 302

    Redirects to the sign-in page.

  • 400

    Invalid SAML request.

  • 404

    The SAML application was not found.

GET /api/saml/{id}/authn 
curl \
 --request GET 'https://[tenant_id].logto.app/api/saml/{id}/authn?SAMLRequest=string' \
 --header "Authorization: Bearer $ACCESS_TOKEN"