Note:
[ ] Authentication & Authorization #1035
[ ] Improve LB4 extensibility PRs
[ ] Migration https://github.com/strongloop/loopback-next/issues/1849
[x] User adoption
[x] Deployment to IBM Cloud
[x] Conference preparation
[ ] Bugs
[ ] Others
[ ] Authentication
UserProfile more flexible https://github.com/strongloop/loopback-next/issues/2246[ ] Bug:
@dhmlau @nabdelgadir According to the estimation meeting yesterday, https://github.com/strongloop/loopback-next/issues/2311 is blocked by https://github.com/strongloop/loopback-next/pull/2249, I propose we work on https://github.com/strongloop/loopback4-example-shopping/issues/40 as a replacement, there is already a PR in progress for it: https://github.com/strongloop/loopback4-example-shopping/pull/33
what would you think?
@jannyHou sounds good to me. @dhmlau what do you think?
@nabdelgadir, @jannyHou and I were just discussing this, and we've modified the milestone.
Based on the discussion summarized in here, the next step for the authentication story is
- Step 1a: create extension point for access token generator in
@loopback/authentication, define the key as the constant and interface
- in shopping example, it will implement this access token generator
- Step 1b: create interface for strategy and then the extension point for strategies -- needs Raymond's PR
- Step 1c: Add common action to authenticate inside authentication module.
- * Step 1d*: Move the credential extractor code from the example app back to the
authenticationpackage.
- Step 2 : rebase shopping example against the
@loopback/authentication
So the stretch goals under authentication epic won't be carried over to March, and @jannyHou will be creating new set of tasks for the above.
Most helpful comment
@nabdelgadir, @jannyHou and I were just discussing this, and we've modified the milestone.