Cockroach: ui: add user/login system

[petermattis]

Add a login system to the UI. The backend has a concept of user, but it isn't currently exposed in the UI. We need a "users" page to list the existing users, add/remove users and change privileges. Users would have to login to the UI and, depending on their privileges, would have a restricted view of the system. This work should be done in TBD stages.

[dianasaur323]

Adding a note here that /debug pages should also sit behind the user / login system as per conversation with @mrtracy

Let's also make sure this gets protected: https://github.com/cockroachdb/cockroach/pull/15908?utm_campaign=Release%20Notes&utm_source=hs_email&utm_medium=email&utm_content=52644291&_hsenc=p2ANqtz-9Im3ECEgB0tiXMffLC23QbvzTPiI-QQh8pYxhIcFPCLhgXlwu-danjdm1PD1PRT1nXc5NnqhtkO20dRXVW5T7rzKGVMA&_hsmi=52644291

[dianasaur323]

Updating this GitHub issue with finalized 1.1 scope - just basic user login with error messages and login ID in the top right. We also need to consider how these logins reflect in logging in case users want to audit usage. cc @kuanluo

https://github.com/cockroachdb/cockroach/blob/69f24571ef0bdc75fd78da6cb400c0933e586c8e/pkg/security/auth.go#L126-L143 --> sampling of existing error messages.

[kuanluo]

Login with field error:

If the error is more generic:

Log out button with ID top right:

cc: @bdarnell @mrtracy

[dianasaur323]

One final fix here on the mocks is to remove the side nav bar on the login page since those buttons won't work anyway. cc @nstewart

[dianasaur323]

punting to 1.2 due to risk of this breaking user workflow without sufficient QA time.

[a-robinson]

If the entire UI requires login, and login requires the database to be working properly, will we no longer be able to use the UI (including the debug pages) to debug broken clusters?

[nstewart]

cc @piyush-singh re: @a-robinson 's question. Let's make sure we don't remove an important debugging workflow

[vilterp]

Closing this since login is implemented and now enabled by default in secure clusters. #29270 tracks @a-robinson's concern that this will block debugging flows.