-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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: Create UI components for login screen #24939
Labels
A-webui-security
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Milestone
Comments
knz
added
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
and removed
feature
labels
Apr 24, 2018
5 tasks
craig bot
pushed a commit
that referenced
this issue
May 22, 2018
25005: ui: add top-level LoginContainer: require login before rendering anything r=couchand a=vilterp Depends on #25057 Touches #24939 ![](https://user-images.githubusercontent.com/7341/39150096-38b4cd28-470f-11e8-9d67-e1832d35a211.gif) Shown above: 1. go to admin UI; see login screen 2. error message when you type in the wrong password 3. you can't hit an authenticated endpoint because you don't have a valid session (this checking is turned on by #24944, only in secure mode) 4. once you login with the right password, you can see the UI (the temporary "connection lost" banner shouldn't be there) 5. now you (and the UI itself) can hit endpoints, because you have a valid session Todos: - [ ] redirect to login page instead of current wrapper component switching thing - [ ] logout - [ ] logout button (make API call; redirect to login & blow away redux store) - [ ] log out other tabs (if they get a 403, redirect to login & blow away redux store) - [ ] styling Release note: None 25628: distsql: support lookup join on secondary index r=solongordon a=solongordon joinReader now supports lookup joins on secondary indexes. This was a trivial change for queries where all the output columns are included in the secondary index. I just modified the physical planner to specify the secondary index in the JoinReaderSpec and removed checks which prevented secondary indexes from being used. The more complicated situation is when we want to do a lookup join against a non-covering index. In this case, the logical planner plans an index join before the inner join, but we want to perform the lookup join first. We now handle this by only planning the lookup join during physical planning, not the index join. During execution, the joinReader detects that there are output columns not covered by the secondary index, and it performs primary index lookups as necessary to retrieve the additional columns. Fixes #25431 Co-authored-by: Pete Vilter <[email protected]> Co-authored-by: Andrew Couch <[email protected]> Co-authored-by: Solon Gordon <[email protected]>
couchand
added a commit
to couchand/cockroach
that referenced
this issue
May 29, 2018
Add some initial styling to the login page. Contributes to cockroachdb#24939. Release note: None
couchand
added a commit
to couchand/cockroach
that referenced
this issue
May 29, 2018
Add some styling and clean up the error text on login page. Contributes to cockroachdb#24939. Release note: None
couchand
added a commit
to couchand/cockroach
that referenced
this issue
Jun 4, 2018
Add some initial styling to the login page. Contributes to cockroachdb#24939. Release note: None
couchand
added a commit
to couchand/cockroach
that referenced
this issue
Jun 4, 2018
Add some styling and clean up the error text on login page. Contributes to cockroachdb#24939. Release note: None
Merged
couchand
added a commit
to couchand/cockroach
that referenced
this issue
Jun 7, 2018
Add some initial styling to the login page. Contributes to cockroachdb#24939. Release note: None
couchand
added a commit
to couchand/cockroach
that referenced
this issue
Jun 7, 2018
Add some styling and clean up the error text on login page. Contributes to cockroachdb#24939. Release note: None
craig bot
pushed a commit
that referenced
this issue
Jun 7, 2018
26066: ui: style login page r=couchand a=couchand Adds some initial styling to the login page and the login indicator in the navigation sidebar. Sidebar: <img width="710" alt="screen shot 2018-05-29 at 1 59 44 pm" src="https://user-images.githubusercontent.com/793969/40676560-110e3a7e-6349-11e8-812a-9c8e682f5670.png"> Login page: <img width="1274" alt="screen shot 2018-06-04 at 4 28 40 pm" src="https://user-images.githubusercontent.com/793969/40940739-c0c6eb10-6816-11e8-9b24-8a0b492239b3.png"> Login page with error: <img width="1277" alt="screen shot 2018-06-04 at 4 45 40 pm" src="https://user-images.githubusercontent.com/793969/40940744-c4cb2d66-6816-11e8-90d4-d8b3c52927b6.png"> Insecure mode (temporary design): <img width="161" alt="screen shot 2018-06-04 at 5 10 56 pm" src="https://user-images.githubusercontent.com/793969/40942388-016f9478-681c-11e8-929c-36d0b7aa7463.png"> Closes #24939. Co-authored-by: Andrew Couch <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-webui-security
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Sub-task for #6307.
This issue is to track front end work for authenticating users as outlined in the above issue. Some states we should consider:
Including an early design from Kuan that was added in the above issue:
@josueeee as discussed, this will need some design attention. cc @vilterp and @couchand
The text was updated successfully, but these errors were encountered: