-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add abstraction for authentication strategy #2466
Comments
How is this story different from #2311 and #2312? Is it a pre-requisite that must be implemented first, before we can work on an extension point? As I wrote in #2312 (comment), I think the authentication strategy abstraction should be defined around what LoopBack-specific strategies need and allow us to write an adapter to convert Passport strategies into LoopBack strategies. What I am trying to say: The approach shown in the current version of |
This story simply creates the interface for auth strategy, the interface will be mostly the same as what is proposed in the design file |
@bajtos we have done oauth 2 integration as a separate component in our LB4 application very recently. We followed the guidelines shared here. I am not too sure what different aspect is getting implemented here or any of the authentication tasks. But if there is any way I can help/contribute, do let me know. I can share our implementation as well, if needed. That's not so robust but it was workable for us. We also did authorisation component but I would mention that in the appropriate issue. |
Feature
Define an interface to describe the authentication strategy. It should contain
authenticate
that verifies the request.functionauthenticate
should take in anoption
to perform the auth action accordingly.Acceptance Criteria
Parent story see #1035 (comment) (step 1b)
The text was updated successfully, but these errors were encountered: