From b6a2bdc00bcf769f087937f8a0021927ff40c414 Mon Sep 17 00:00:00 2001 From: Ryan Godfrey Date: Wed, 5 Nov 2025 13:31:24 -0500 Subject: [PATCH] added note about origin setting for authentication providers --- .../cluster-or-deployment-auth/kibana-authentication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication.md b/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication.md index c0c5a8da9f..cf96bd1a32 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication.md @@ -36,7 +36,7 @@ To provide login instructions to users, use the `xpack.security.loginHelp` setti :::: -If you don’t want a specific provider to show up at the Login Selector UI (e.g. to only support third-party initiated login) you can hide it with `showInSelector` setting set to `false`. However, in this case, the provider is presented in the provider chain and may be consulted during authentication based on its `order`. To disable the provider, use the `enabled` setting. +If you don’t want a specific provider to show up at the Login Selector UI (for example, if you only want to support third-party initiated login) you can hide it with `showInSelector` setting set to `false`. Or, if you only want to show a provider for a specific origin(s), you can use the `origin` setting. However, in both cases the provider is still part of the provider chain and may be used during authentication based on its order. To fully disable a provider, use the `enabled` setting. ::::{tip} The Login Selector UI can also be disabled or enabled with `xpack.security.authc.selector.enabled` setting.