-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ui: Login Flow for Admin UI #18206
Comments
Draft Acceptance Criteria - Accepting Comments User Story Feature Scope
Required States
PM Acceptance Testing
|
Closes: cockroachdb#6307 Closes: cockroachdb#18206 Closes: cockroachdb#26518 Release note (admin ui change): Login is now required for secure clusters. Users log in with a regular database username, so that user must already have a password set. Insecure clusters do not require login, and have a visual indicator showing that they are insecure.
Closes: cockroachdb#6307 Closes: cockroachdb#18206 Closes: cockroachdb#26518 Release note (admin ui change): Login is now required for secure clusters. Users log in with a regular database username, so that user must already have a password set. Insecure clusters do not require login, and have a visual indicator showing that they are insecure.
Closed in #28416 |
The Admin API now fully supports cookie-based authentication, which will restrict admin functions to authenticated users. However, the UI does not currently provide a way for a user to authenticate, so that system has been disabled in 1.1.
A login page should be added to the frontend, and all other activities on the Admin UI should be protected by that login. Details are available in the "web_session_login" RFC found under
/docs/RFCS
.Works towards #6307
The text was updated successfully, but these errors were encountered: