Skip to content
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

Closed
1 task
deepakrkris opened this issue Mar 31, 2020 · 4 comments
Closed
1 task

Comments

@deepakrkris
Copy link
Contributor

deepakrkris commented Mar 31, 2020

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:

  • 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.
@deepakrkris
Copy link
Contributor Author

IMO, this issue can wait for #5118 , to inject express style middleware into controller calls and sequence invocations

@deepakrkris
Copy link
Contributor Author

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

@dhmlau dhmlau removed this from the May 2020 milestone Apr 21, 2020
@deepakrkris deepakrkris removed their assignment Apr 25, 2020
@dhmlau dhmlau removed the 2020Q2 label May 12, 2020
@stale
Copy link

stale bot commented Dec 25, 2020

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 CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

@stale stale bot added the stale label Dec 25, 2020
@stale
Copy link

stale bot commented Jul 14, 2021

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 CODEOWNERS file at the top-level of this repository.

@stale stale bot closed this as completed Jul 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants