There are number of authentication screens we have in Kibana that are rarely seen by our users and hence we don't touch them very often too. But I believe it makes sense to periodically review them with the Design and Docs Teams to make sure the texts are still relevant and UX is consistent.
Edit 2022-02-01: Add screenshot tests for visuals
Edit 2022-11-14: @watson to include one more screen when CSP isn't supported by the user's browser ✅
Edit 2022-11-15: Added screenshot with message for unsupported browser
Fail states of the Login Form/Selector
- When administrators mistakenly or not configured Kibana in a way that it doesn't allow any authentication mechanisms:

- When administrators configured Kibana to use
Secure cookies, but didn't configure Kibana to use TLS (a strict requirement in this case):

- When Elasticsearch isn't available

- When Elasticsearch is available, but we cannot retrieve current license for some reason

- Unexpected error during login page rendering (it should never happen in theory, if it happens it's most likely a bug in our code or some weird network glitch)

Logout related messages
- When user hits logout button and Login Selector/Form is enabled (the most common use case these days)

- When user hits logout button and Login Selector/Form is NOT enabled. I thought maybe it'd make sense to unify wording in this case with the case above? The only problem is that the font is larger on this screen and the message will be split into multiple lines unless we change styles.

- When Kibana forces user to log out because of expired session and Login Selector/Form is enabled

- When Kibana forces user to log out because of expired session and Login Selector/Form is NOT enabled. It looks exactly the same as the case when user decides to log out on their own. Would probably make sense to change the wording here as well, but again the current font size may be a problem. I'm explicitly calling out the font size since this page/component is re-used in other cases (access agreement and overwritten session screen described below) that will be affected if we change the font size.

Other messages
- When user happens to automatically re-login when they already had an active session as a different user (quite rare case, but it happens)

- If the users browser doesn't support CSP, this message will be displayed. An easy to to reproduce this is to remove the CSP header from the response and launch Kibana

There are number of authentication screens we have in Kibana that are rarely seen by our users and hence we don't touch them very often too. But I believe it makes sense to periodically review them with the Design and Docs Teams to make sure the texts are still relevant and UX is consistent.
Edit 2022-02-01: Add screenshot tests for visuals
Edit 2022-11-14: @watson to include one more screen when CSP isn't supported by the user's browser ✅
Edit 2022-11-15: Added screenshot with message for unsupported browser
Fail states of the Login Form/Selector
Securecookies, but didn't configure Kibana to use TLS (a strict requirement in this case):Logout related messages
Other messages