-
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
Migrate apps using loopback-component-passport with LB3 Composition #5005
Comments
IMO, this issue can wait for #5118 , to inject express style middleware into controller calls and sequence invocations |
this is essentially not a high priority task, given that there are better options coming up for migrating express styled apps to lb4 , with #5118 |
This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the |
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the |
This is a follow-up for #3718 and #3922.
Scoped from #3958
Write content for
docs/site/migration/auth/passport.md
, explain how to migrate LB3 applications using loopback-component-passport to LB4.For short to medium term, while users are running both LB3 and LB4 app at the same time, we can show them how to use Passport as Express middleware, see #3947.
Acceptance criteria
Migration guide describing manual steps for the following scenarios:
The text was updated successfully, but these errors were encountered: