Configuration option to add custom link and text to Kibana login screen

[alexfrancoeur]

Some users would like a link to either ticketing system and/or page where users can request access, reset passwords, modify access. This way, when users hit Kibana for the first time and don't have access, they have somewhere to go to request access.

More generally, the ability to add a custom html site link to login page for admin user to specify text of the link and link to external page through the management interface in Kibana.

I added the platform label, but I'm not sure if that's the correct team.

[elasticmachine]

Pinging @elastic/kibana-platform

[gmarziou]

We currently have 2 deployments in Elastic cloud and users often make mistakes because they can't differentiate them visually and the AWS URLs don't help. As a temporary workaround, as both deployments are running 6.x we enabled 7.0 design preview on one of them but as soon as we upgrade them to 7.x we will lose this feature and so this is blocking us from upgrading.

Being able to add custom text on login screen would be useful or at least being able to display the deployment name. The same requirement applies also for Kibana other pages, we would like to be able to visually identify the deployment in Kibana's top banner.

[mbarretta]

@alexfrancoeur is this related to #18176?

[C0FFEEC0FFEE]

Currently we are using the notifications:banner setting for a similar purpose. However this needs to be configured for each space individually and is only displayed after opening said space.

We'd very much benefit from this feature as it would spare us the hassle of setting a banner in each space for global announcements.

[legrego]

This may be resolved by #51557, which introduced a new xpack.security.loginAssistanceMessage kibana.yml setting. This allows for markdown to be specified, similar to the following:

@alexfrancoeur does #51557 satisfy your requirements here?

Barring any unforeseen issues, #51557 is slated for version 7.6.

[alexfrancoeur]

@legrego thanks for following up on this. I believe it does meet this requirements defined in the description. Great to see this in 7.6, I'll close the relevant ER's!