[authorization] userToPrinciple using incorrect id/securityId

[JohnLindahlTech]

Steps to reproduce

The userToPrinciple method in authZ breaks current UserProfile at the following line:
https://github.com/strongloop/loopback-next/blob/81890fce1e5cdaf1821557537164f23ba687386b/packages/authorization/src/authorize-interceptor.ts#L160

Current Behavior

As you can see the method basically throws the securityId away (by setting it to the name) and tries to set the id (which no longer is valid in UserProfile to securityId on the principal.
So from here on, currentUserProfile always has an undefined securityId.

Expected Behavior

The principal which is used in authorizors ( currentUser = authorizationCtx.principals[0];) should have a working securityId.

tagging @raymondfeng @jannyHou as the usual suspects :)

Using:

├─┬ @loopback/[email protected]
│ └── @loopback/[email protected]  deduped
├─┬ @loopback/[email protected]
│ └── @loopback/[email protected]  deduped
└── @loopback/[email protected]

[dhmlau]

Thanks @JohnPhoto for tagging them. :)

@jannyHou @raymondfeng , could you please take a look? Thanks.

[jannyHou]

@JohnPhoto we released @loopback/[email protected] which is compatible with @loopback/[email protected], can you try them?

[JohnLindahlTech]

Those are the ones I am using as you can see in my edit of my original post.

[derdeka]

Related to #3766

[derdeka]

Fixed with #3807 ?

[derdeka]

@jannyHou @raymondfeng @JohnPhoto
Is the issue resolved as #3807 is merged?

[dhmlau]

Closing as resolved.