Repository navigation
Extension: Add Authorization component #538
Description
Related to #512
- decoration at controller/method level may not be flexible enough
- URL-based rules as an alternative
- fine-grained access control on per-model-instance basis - ideally solved at Repository level
- local User/AccessToken auth scheme and models
- ACL/Role-based rules vs. scope-based rules
- JWT
- OAuth
Reacted by M. Berchten, Douglas McConnachie, Clay Risser, Aidan Harbison, Matteo Padovano, bbenejc, L. Bete, Akash Jarad, Peter, globaltommy and 1 more
Reacted by L. Bete and Akash Jarad
Reacted by L. Bete and globaltommy
Activity
dhmlau commentedon Aug 24, 2017
Marking as
Core-GAper our discussion.21 remaining items
docs: add guideline doc for authorize component
docs: add guideline doc for authorize component
samarpanB commentedon Apr 20, 2019
@raymondfeng I was trying to look for the doc page on https://loopback.io/doc/en/lb4/Using-components.html. But it’s not there yet. Is it not yet moved there ? As per my understanding, there is a daily job which moves it there.
raymondfeng commentedon Apr 20, 2019
We need to publish a release to npm 1st.
raymondfeng commentedon Apr 20, 2019
@samarpanB I just made a release. The document site will be updated soon.
dhmlau commentedon Apr 22, 2019
@samarpanB, it's up: https://loopback.io/doc/en/lb4/Loopback-component-authorization.html. Thanks for your contribution!
dougal83 commentedon May 8, 2019
Thanks for your work @samarpanB. I've just been looking at your implementation.
Could I ask if there are plans to map roles to scopes at this point in time? Personally I'd find an implementation or roles based on oath scopes a logical path to follow especially in conjunction jwt for auth.
EDIT: NM Found this: #1035 (comment)
raymondfeng commentedon May 15, 2019
See #1205
dhmlau commentedon Aug 21, 2019
Closing as done.