This repository was archived by the owner on Jul 22, 2021. It is now read-only.
[NIFIREG-30] add login component, auth guard to login, tenants, bucke…#58
Closed
scottyaslan wants to merge 1 commit intoapache:masterfrom
Closed
[NIFIREG-30] add login component, auth guard to login, tenants, bucke…#58scottyaslan wants to merge 1 commit intoapache:masterfrom
scottyaslan wants to merge 1 commit intoapache:masterfrom
Conversation
…ts, admin, and explorer routes. Also added route for login component. [NIFIREG-20] improve page load times. [NIFIREG-15] add loading screen.
Contributor
|
Functionality looks good, awesome to control the user privileges through the UI in secure mode! Going to merge this |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…ts, admin, and explorer routes. Also added route for login component. [NIFIREG-20] improve page load times. [NIFIREG-15] add loading screen.
In an unsecured registry an anonymous user should be able to access:
http://localhost:8080/nifi-registry/login
http://localhost:8080/nifi-registry/administration/workflow
http://localhost:8080/nifi-registry/explorer/grid-list
an attempt to access http://localhost:8080/nifi-registry/administration/users will reroute the user to the login screen (as will any other attempt to access a deep link to which a user does not have access to).
an attempt to access an unknown route (http://localhost:8080/nifi-registry/abcef) will prompt the user with a dialog to click to easily access http://localhost:8080/nifi-registry/explorer/grid-list
In a secured registry the user should only have access to the routes for which they have permissions. If the user is logging in via certs or kerberos the client recognizes this and routes the user to the http://localhost:8080/nifi-registry/explorer/grid-list.