-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Ensure legacy users with authData are not locked out #4898
Conversation
cabeb23
to
8b0192e
Compare
I confirm this solves #4897 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks Like CI doesn't like this PR
src/RestWrite.js
Outdated
} | ||
return objects.filter((object) => { | ||
if (!object.ACL) { | ||
return true; // legacu users that have no ACL field on them |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
*legacy
8b0192e
to
a79f576
Compare
Codecov Report
@@ Coverage Diff @@
## master #4898 +/- ##
==========================================
- Coverage 92.92% 92.87% -0.06%
==========================================
Files 119 119
Lines 8830 8836 +6
==========================================
+ Hits 8205 8206 +1
- Misses 625 630 +5
Continue to review full report at Codecov.
|
* Adds fix for issue, ensuring legacy users with no ACL are properly handled * Runs tests only on mongo
* Adds fix for issue, ensuring legacy users with no ACL are properly handled * Runs tests only on mongo
…#4898) * Adds fix for issue, ensuring legacy users with no ACL are properly handled * Runs tests only on mongo
Fixes #4897
When adding the feature with user lockout, this added an issue as legacy users, ones without ACL's would be locked out of their account, unable to login.
The fix is to ignore those accounts where the ACL is undefined and not treat it as a locked out ACL.