/login

Hosted sign-in page for the M7 SSO flow.

Endpoint

  • Method: GET
  • URL: https://sso.user.m7.org/login
  • Response: hosted HTML page

When to use it

Use this route if you explicitly want to send the user to the hosted sign-in page.

For most OAuth and OIDC integrations, the preferred browser entrypoint is still /authorize.

Query parameters

The page accepts authorization context such as:

  • client_id
  • redirect_uri
  • scope
  • state
  • code_challenge
  • code_challenge_method
  • nonce
  • login_hint
  • request_uri

If you are using PAR, request_uri can be used here as well.

Example

https://sso.user.m7.org/login?client_id=CLIENT_ID&redirect_uri=https%3A%2F%2Fapp.example.com%2Fcallback&scope=openid%20profile&state=STATE123&code_challenge=PKCE_CHALLENGE&code_challenge_method=S256

What happens next

The hosted page collects the user's sign-in information and then continues the authorization flow for the supplied client context.

Notes

  • client_id and redirect_uri are validated before the page is shown.
  • This route is a hosted browser page, not a JSON API.