Clarify authentication providers orders in the Serverless test config. (#166356)

## Summary

Clarify authentication providers orders in the Serverless test config.

__Follow-up for:__
https://github.com/elastic/kibana/pull/165810#discussion_r1324364175
This commit is contained in:
Aleh Zasypkin 2023-09-14 14:14:51 +02:00 committed by GitHub
parent 6968fe171a
commit 0538e65a8b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -121,6 +121,11 @@ export default async () => {
// In the real world the SAML config is injected by control plane.
`--plugin-path=${samlIdPPlugin}`,
'--xpack.cloud.id=ftr_fake_cloud_id',
// Ensure that SAML is used as the default authentication method whenever a user navigates to Kibana. In other
// words, Kibana should attempt to authenticate the user using the provider with the lowest order if the Login
// Selector is disabled (which is how Serverless Kibana is configured). By declaring `cloud-basic` with a higher
// order, we indicate that basic authentication can still be used, but only if explicitly requested when the
// user navigates to `/login` page directly and enters username and password in the login form.
'--xpack.security.authc.selector.enabled=false',
`--xpack.security.authc.providers=${JSON.stringify({
saml: { 'cloud-saml-kibana': { order: 0, realm: 'cloud-saml-kibana' } },