Skip to content

Conversation

@bajtos
Copy link
Member

@bajtos bajtos commented Mar 20, 2018

Fix the bug where the access context was created with incorrect principal type when the application has multiple user models configured, and custom roles were not honored as a result.

Close #3829

@akki-ng This patch is inspired by your #3823 but fixes a different and smaller problem. Could you please take a look at the proposed code changes too?

@ebarault If you can, then please review my changes too, they are related to you work on multi-user-model support.

@akki-ng
Copy link

akki-ng commented Mar 20, 2018

LGTM.

@bajtos bajtos merged commit 77d3d57 into master Mar 22, 2018
@bajtos bajtos deleted the fix/role-acl-with-multiple-users branch March 22, 2018 08:18
@akki-ng
Copy link

akki-ng commented Mar 22, 2018

@bajtos I did not get any notification for CLA. Can this be done now?

@bajtos
Copy link
Member Author

bajtos commented Mar 22, 2018

@akki-ng the commit was authored by myself only, that's why no CLA check was triggered for you. We will deal with CLA in the other pull request you have sent yourself. For reference, this is the URL where you can sign: https://cla.strongloop.com/agreements/strongloop/loopback

@akki-ng
Copy link

akki-ng commented Mar 22, 2018

@bajtos Cool. Thanks for the update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ACL seems to not work when having multiple user models with a base UserModel

4 participants