-
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
Extension point for registering the authentication strategies #2312
Comments
37 tasks
This was referenced Jan 31, 2019
jannyHou
changed the title
Extension point for registering the custom authentication action
Extension point for registering the non-passport based authentication strategies
Feb 28, 2019
IMO, we should design the extension point for auth strategies in the following way:
|
This was referenced Mar 5, 2019
I think this story depends on #2466: Add abstraction for authentication strategy. |
Sounds good to me. There is already an adapter in |
jannyHou
changed the title
Extension point for registering the non-passport based authentication strategies
Extension point for registering the authentication strategies
Mar 25, 2019
7 tasks
This was referenced Apr 11, 2019
7 tasks
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description / Steps to reproduce / Feature proposal
Follow the extension pattern example to create extension point for registering multiple authentication strategies.
Background of the story:
Now we implement a new provider in a hardcoded way to perform the authenticate action of the custom jwt strategy created by ourselves, see custom authentication provider.
This should be an extensible point that people can plugin the actions for both passport and non passport-based strategies.
Acceptance Criteria
AuthenticationStrategyProvider
with@extensionPoint
@extensions
AuthenticateActionProvider
to useAuthenticationStrategy
interface and the new strategy provider classSee Reporting Issues for more tips on writing good issues
The text was updated successfully, but these errors were encountered: