Get Endpoint Settings
Read an endpoint's auth configuration — its mode, enabled sign-in methods, session TTL, HTTPS enforcement and the config object (login page, protected paths, registration) — as PUT /v1/endpoints/{uuid}/settings stored it. Credentials are not part of it: they belong to the endpoint's Access Control clients and OAuth providers. JWT checks are jwt-validation traffic policy rules, listed with the endpoint's traffic policies.
Use this to render the dashboard's auth-config screen, or to back up an endpoint's auth state before re-applying it elsewhere.
Path parameters
Response (200 OK)
{uuid} in the path).none or basic. SSO reads back as basic with enabled_auth_methods.oauth_sso: true (a PUT of "sso" is stored that way). An endpoint configured before these changes can still return token, header, cookie or jwt: those modes are not supported, and the edge refuses every request to the endpoint (401) until you set none, basic or sso with PUT /v1/endpoints/{uuid}/settings.basic: the login page (title, message, button_label) and which paths need a sign-in (protect_all, protected_paths). For other modes: the stored config as is (e.g. registration). Omitted when there is none — always so on an endpoint whose auth was never configured.{"username_password": bool, "bearer_token": bool, "oauth_sso": bool}. Omitted when never set (including on an endpoint whose auth was never configured) — then every method is on. All three false means the endpoint requires no sign-in, whatever the mode.An endpoint whose auth was never configured answers with only endpoint_uuid, mode: "none" and enforce_https: false.
Deprecated: until the sunset this response also carries the legacy integer endpoint_id. Don't use it; read endpoint_uuid.