-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Improve email verification #3681
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
Merged
flovilmart
merged 3 commits into
parse-community:master
from
aontas:improveEmailVerification
May 11, 2017
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2784,4 +2784,121 @@ describe('Parse.User testing', () => { | |
done(); | ||
}); | ||
}); | ||
|
||
it('should not allow updates to emailVerified', done => { | ||
var emailAdapter = { | ||
sendVerificationEmail: () => {}, | ||
sendPasswordResetEmail: () => Promise.resolve(), | ||
sendMail: () => Promise.resolve() | ||
} | ||
|
||
const user = new Parse.User(); | ||
user.set({ | ||
username: 'hello', | ||
password: 'world', | ||
email: "[email protected]" | ||
}) | ||
|
||
reconfigureServer({ | ||
appName: 'unused', | ||
verifyUserEmails: true, | ||
emailAdapter: emailAdapter, | ||
publicServerURL: "http://localhost:8378/1" | ||
}).then(() => { | ||
return user.signUp(); | ||
}).then(() => { | ||
return Parse.User.current().set('emailVerified', true).save(); | ||
}).then(() => { | ||
fail("Should not be able to update emailVerified"); | ||
done(); | ||
}).catch((err) => { | ||
expect(err.message).toBe("Clients aren't allowed to manually update email verification."); | ||
done(); | ||
}); | ||
}); | ||
|
||
it('should not retrieve hidden fields', done => { | ||
|
||
var emailAdapter = { | ||
sendVerificationEmail: () => {}, | ||
sendPasswordResetEmail: () => Promise.resolve(), | ||
sendMail: () => Promise.resolve() | ||
} | ||
|
||
const user = new Parse.User(); | ||
user.set({ | ||
username: 'hello', | ||
password: 'world', | ||
email: "[email protected]" | ||
}) | ||
|
||
reconfigureServer({ | ||
appName: 'unused', | ||
verifyUserEmails: true, | ||
emailAdapter: emailAdapter, | ||
publicServerURL: "http://localhost:8378/1" | ||
}).then(() => { | ||
return user.signUp(); | ||
}).then(() => rp({ | ||
method: 'GET', | ||
url: 'http://localhost:8378/1/users/me', | ||
json: true, | ||
headers: { | ||
'X-Parse-Application-Id': Parse.applicationId, | ||
'X-Parse-Session-Token': Parse.User.current().getSessionToken(), | ||
'X-Parse-REST-API-Key': 'rest' | ||
}, | ||
})).then((res) => { | ||
expect(res.emailVerified).toBe(false); | ||
expect(res._email_verify_token).toBeUndefined(); | ||
done() | ||
}).then(() => rp({ | ||
method: 'GET', | ||
url: 'http://localhost:8378/1/users/' + Parse.User.current().id, | ||
json: true, | ||
headers: { | ||
'X-Parse-Application-Id': Parse.applicationId, | ||
'X-Parse-REST-API-Key': 'rest' | ||
}, | ||
})).then((res) => { | ||
expect(res.emailVerified).toBe(false); | ||
expect(res._email_verify_token).toBeUndefined(); | ||
done() | ||
}).catch((err) => { | ||
fail(JSON.stringify(err)); | ||
done(); | ||
}); | ||
}); | ||
|
||
it('should not allow updates to hidden fields', done => { | ||
var emailAdapter = { | ||
sendVerificationEmail: () => {}, | ||
sendPasswordResetEmail: () => Promise.resolve(), | ||
sendMail: () => Promise.resolve() | ||
} | ||
|
||
const user = new Parse.User(); | ||
user.set({ | ||
username: 'hello', | ||
password: 'world', | ||
email: "[email protected]" | ||
}) | ||
|
||
reconfigureServer({ | ||
appName: 'unused', | ||
verifyUserEmails: true, | ||
emailAdapter: emailAdapter, | ||
publicServerURL: "http://localhost:8378/1" | ||
}).then(() => { | ||
return user.signUp(); | ||
}).then(() => { | ||
return Parse.User.current().set('_email_verify_token', 'bad').save(); | ||
}).then(() => { | ||
fail("Should not be able to update email verification token"); | ||
done(); | ||
}).catch((err) => { | ||
expect(err).toBeDefined(); | ||
done(); | ||
}); | ||
}); | ||
}); |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
just a quick question,
Those fields get stripped only when calling /me, but not when let's say we make an unauthenticated query?
Could we add a test for that?
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.
What sort of unauthenticated query would we want these fields to be available?
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.
That's the point, we won't. But those fields would only be stripped here, not everywhere we need them to be stripped
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.
There does seem to be handling somewhere that removes hidden fields (see updated test where users/ is retrieved without hidden field).
The general case where all hidden fields are removed from all unauthenticated queries is likely better to be talked in its own issue, rather than tacked on to this PR.
Does this current version require any further changes?