"no connections enabled for the client" error when only "email" connection is enabled

Hi there,

We’re seeing “no connections enabled for the client” error when redirecting to the Auth0 sign-in page, but “email” connection is actually enabled for this client.

  • “organization” and “connection” parameters are set in authorizationParams. connection param is set to “email”.
  • Authentication Profile is set as “Identifier First”.
  • only “email” connection(Passwordless) exists in the tenant, and it’s enabled for the organization and the client.
  • New Universal Login UI is enabled.
  • Tenant is in JP-1 region.

Is there any way to have “email” connection as the only connection, or do we have to create another connection even if it is not used?

The following is the actual error log.

  "date": "2023-05-19T01:13:04.415Z",
  "type": "f",
  "description": "no connections enabled for the client",
  "connection": "email",
  "connection_id": "XXX",
  "client_id": "XXX",
  "client_name": "XXX",
  "ip": "XXXX",
  "user_agent": "Chrome 113.0.0 / Mac OS X 10.15.7",
  "details": {
    "body": {},
    "qs": {
      "client_id": "XXX",
      "scope": "openid profile",
      "audience": "XXX",
      "redirect_uri": "XXX",
      "organization": "XXX",
      "connection": "email",
      "response_type": "code",
      "response_mode": "query",
      "state": "/xxx",
      "nonce": "XXX",
      "code_challenge": "XXX",
      "code_challenge_method": "S256",
      "auth0Client": "XXX"
    "connection": "email",
    "error": {
      "message": "no connections enabled for the client",
      "oauthError": "no connections enabled for the client",
      "type": "invalid_request",
      "uri": null
    "session_id": "XXX",
    "riskAssessment": null
  "hostname": "XXX.auth0.com",
  "organization_id": "XXX",
  "organization_name": "XXX",
  "audience": "XXX",
  "scope": [
  "auth0_client": {
    "name": "auth0-react",
    "version": "2.1.0"
  "log_id": "XXX",
  "_id": "XXX",
  "isMobile": false,
  "id": "XXX"

Thank you,

I was notified by the support team that the problem was due to an internal issue which has been resolved now.

1 Like

Thanks for sharing it with the rest of community!

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.