You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For short to medium term, while they are running both LB3 and LB4 app at the same time, we can show them how to use Passport as Express middleware, see #3947.
scoped to #5005
Acceptance criteria
Migration guide describing manual steps for the following scenarios:
This is a follow-up for #3718 and #3922.
Write content for
docs/site/migration/auth/passport.md
, explain how to migrate LB3 applications using loopback-component-passport to LB4.I think the long term goal should be to move our users to
@loopback/authentication-passport
.For short to medium term, while they are running both LB3 and LB4 app at the same time, we can show them how to use Passport as Express middleware, see #3947.scoped to #5005
Acceptance criteria
Migration guide describing manual steps for the following scenarios:
LB4-only, this should show how to migrate to our recommended setup. (PR : docs: migrate loopback-example-passport repo as lb4 example #4899)
Both LB3 and LB4 applications running in the same process, we want to use a single passport configuration to secure both LB3 and LB4 routes.scoped into a separate issue: Migrate apps using loopback-component-passport with LB3 Composition #5005
The text was updated successfully, but these errors were encountered: