[Console] Use of localStorage

[jloleysens]

Console uses localStorage to persist the current user's inputted text and last 500 requests across usage sessions. Use of localStorage in this way has the following issues:

Security issue

Shared between all users of the browser instance. The degree to which this is a problem depends on the sensitivity of the text stored and who has access to the computer and browser.

Storage issue

localStorage has a quota of 10mb that is shared among all plugins on Kibana. This can lead to a situation where Console fills up localStorage (e.g., #78014) and can cause issues for other plugins trying to save data there. E.g., the news feed entries:

Solution

Console should migrate away from storing text in localStorage and instead find a more scalable solution. One approach (#56769) is to save all Console state in the ES with encrypted saved objects. The attempted solution incurred the complexity of managing secure access to stored objects, which seemed like a solution that could be required in multiple places in Kibana. Once this is figured out, it seems as though this might be the most scalable and secure way of storing user inputs with the added benefit that a user will have their Console state available no matter which browser they have logged in with.

[elasticmachine]

Pinging @elastic/es-ui (Team:Elasticsearch UI)

[cjcenizal]

save all Console state in the ES with encrypted saved objects

I believe this will be addressed in a centralized manner by the Core team via #17888.

[cjcenizal]

See #23488 for more context. That issue has a lot of likes and also some more anecdotal data.

[cjcenizal]

Also relates to #39017, which requests that Console history be space-aware.

[elasticmachine]

Pinging @elastic/kibana-management (Team:Kibana Management)