-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Loopback PUT Request turn emailVerified to "false" #3059
Comments
Experiencing the same problem here. We have an admin tool that sets emailVerified to true via a pot request, but it stopped working. |
This appears to be caused by a change in v2.36.2, which is attempting to set emailVerified to false when a user changes their email address. This should ONLY happen when the email address actually changes, not ANY time a user record is modified! |
It doesn't, this happen any change you do in the User's model. |
Temporary workaround for those in need: |
Tomorrow I'll check this update, thanks.
Il giorno mar 10 gen 2017 alle ore 22:07 David Cheung <
[email protected]> ha scritto:
Closed #3059 <#3059>.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3059 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ANKEvNSDlThnEAZhdNo3mY-DAb7ZlpI4ks5rQ_L1gaJpZM4LYBsP>
.
--
{"name":"Gaetano Cerniglia",
"email":"[email protected]",
"skype":"gaetano.cerniglia",
"tel":"3458161655"}
|
tl;dr... was/is this an issue for loopback 3.x.x? |
Bug or feature request
Description of feature (or steps to reproduce if bug)
I tried a Put request with Loopback Explorer - it turns emailVerified to false, and thats why I am unable to login user.
Link to sample repo to reproduce issue (if bug)
Expected result
Should remain True
Actual result (if bug)
Additional information (Node.js version, LoopBack version, etc)
The text was updated successfully, but these errors were encountered: