Skip to content
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

Route security implementation [A discussion] #90

Open
silverbackdan opened this issue Jun 4, 2020 · 0 comments
Open

Route security implementation [A discussion] #90

silverbackdan opened this issue Jun 4, 2020 · 0 comments
Labels
help wanted Extra attention is needed question Further information is requested

Comments

@silverbackdan
Copy link
Collaborator

I have been battling with my own thoughts on the best way to implement this. Please take a look at how the bundle configuration can currently be used to determine route security and perhaps we can discuss the flexibility of this for applications.

The results need to be able to be the following:

  1. Collections only return routes for which the current user (or anonymous user) has access to.
  2. Route resource items which are not authorised must return 401/403 (not just a 404 not found).

Any input and discussion is greatly appreciated.

@silverbackdan silverbackdan added help wanted Extra attention is needed question Further information is requested labels Jun 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant