Creating adapter for the plugged in passport strategies

[jannyHou]

Description / Steps to reproduce / Feature proposal

We should allow users to plugin custom passport strategies like passport-jwt. I tried replacing our own implementation of jwt strategy with the community one passport-jwt in PR loopbackio/loopback4-example-shopping@3cbb0a8 to verify it works with our current @loopback/authentication module, the missing part is make the strategy registration flexible.

Acceptance Criteria

• Allow developers to register their own passport strategy
• A reference for the implementation would be how we register a custom body parser in the application, see this test case we have the extension point now 🎉
• Please note that this extension point only open for passport based strategies, which means when create the binding key/resolve the strategy name, make sure it's for passport particularly.
• The story owner could explorer different approaches other than the way we register custom body parser.

See Reporting Issues for more tips on writing good issues

[bajtos]

As I commented in #2312 (comment), I think our support for Passport strategies should be built on top of a LoopBack-specific extension point described by #2312.

That means we need to implement #2312 before working on this story.

[bajtos]

I think this story depends on #2466: Add abstraction for authentication strategy.

[emonddr]

Some of this work seems to be occurring in the PR for #2467.

[jannyHou]

Some of this work seems to be occurring in the PR for #2467.

+1.

If we agree on the rewrite of adapter in the draft PR #2688, then this story can be closed along with #2467 after the formal version of #2688 get merged

[jannyHou]

The new adapter is published as @loopback/[email protected], an experimental package 🎉 https://www.npmjs.com/package/@loopback/authentication-passport

We've tried 2 approaches:

• wrapping a passport strategy module like passport-http
• wrapping the express middleware passport

It turns out the 1st approach is more consistent with non-passport based strategies and we have need more effort to fully support wrapping an express middleware.

Closing it now.