Skip to content

Management Host Name Required

URI: https://docs.ankatech.co/errors/management-host-name-required
HTTP Status: 409 Conflict

When you see this

An OIDC or SAML identity provider was created, enabled, or its derived URLs were read, on a deployment that has no Management host name yet. Nothing was persisted.

An OIDC provider's redirect URI and a SAML provider's assertion consumer URL and service provider entity ID derive from the deployment's Management host name. A deployment installed in quick-start mode has none until an operator sets it: its Management surface is https://localhost:9443, reached through a private port forward. Until then the platform cannot give a provider the URLs it must register, so it refuses the configuration on the platform plane and on every tenant. An LDAP directory derives no URL from the host name and can be configured as usual.

The answer stays the same until a Management host name is set.

Common Causes

  • The deployment was installed without DNS (quick-start mode, for example from the AWS Marketplace image), and no Management host name has been set yet.
  • A tenant administrator tried to configure the tenant's own identity provider on such a deployment.

Response Example

{
  "type": "https://docs.ankatech.co/errors/management-host-name-required",
  "title": "Management Host Name Required",
  "status": 409,
  "detail": "No Management host name is set for this deployment, so an OIDC or SAML identity provider cannot be configured: its redirect and assertion consumer URLs derive from that host name. Ask an operator to set the Management host name, then configure the provider. An LDAP directory can be configured now.",
  "instance": "/api/v3/admin/platform/idp",
  "timestamp": 1792236600,
  "extensions": {
    "requestId": "4e2a9c71-0b3d-4f58-a6e1-9d7c2b5f8e30"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. This is an Admin API body, so the correlation identifier is extensions.requestId; see Error Index & Overview.

How to Resolve

  1. Ask the deployment's operator to set the Management host name on the environment host: sudo envctl.sh <env> set-management-host <name>. See Quick Start: Without DNS*.
  2. Configure the provider again; its derived URLs then name the host name.
  3. To federate sign-in before a host name exists, configure an LDAP directory instead.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.

* restricted content — see higher-tier documentation