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

Ensure legacy users with authData are not locked out #4898

Merged
merged 2 commits into from
Jul 18, 2018
Merged

Conversation

flovilmart
Copy link
Contributor

@flovilmart flovilmart commented Jul 17, 2018

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.

@flovilmart flovilmart requested a review from dplewis July 17, 2018 21:15
@flovilmart flovilmart changed the title Adds fix for issue, ensuring legacy users with no ACL are properly ha… Ensure legacy users with authData are not locked out Jul 17, 2018
@jose-carballo
Copy link

I confirm this solves #4897

Copy link
Member

@dplewis dplewis left a 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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

*legacy

@codecov
Copy link

codecov bot commented Jul 18, 2018

Codecov Report

Merging #4898 into master will decrease coverage by 0.05%.
The diff coverage is 88.88%.

Impacted file tree graph

@@            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
Impacted Files Coverage Δ
src/Controllers/DatabaseController.js 94.69% <100%> (ø) ⬆️
src/RestWrite.js 93.14% <87.5%> (-0.11%) ⬇️
src/Adapters/Auth/meetup.js 84.21% <0%> (-5.27%) ⬇️
src/Adapters/Storage/Mongo/MongoStorageAdapter.js 91.27% <0%> (-0.75%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b22947d...e1b1466. Read the comment docs.

@flovilmart flovilmart merged commit efb6c63 into master Jul 18, 2018
@flovilmart flovilmart deleted the fix/issue-4897 branch July 18, 2018 14:42
flovilmart added a commit that referenced this pull request Aug 12, 2018
* Adds fix for issue, ensuring legacy users with no ACL are properly handled

* Runs tests only on mongo
flovilmart added a commit that referenced this pull request Aug 12, 2018
* Adds fix for issue, ensuring legacy users with no ACL are properly handled

* Runs tests only on mongo
UnderratedDev pushed a commit to UnderratedDev/parse-server that referenced this pull request Mar 21, 2020
…#4898)

* Adds fix for issue, ensuring legacy users with no ACL are properly handled

* Runs tests only on mongo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Parse.FacebookUtils.logIn is creating new users when Facebook ID already exists.
3 participants