-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
emailVerified issue during User update #3689
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
Comments
Hi @medispanu , I'm experiencing the exact same issue! Everytime the user object will be re-saved. Even if the "email" field did NOT change, it triggers a ne emailVerification... Do you know any solutions or short workarounds to this I could implement? Thanks much for feedback and best regards, |
@code-K @medispanu Having exact same issue for FB login. Did you find any solution? |
Hi Junal,
I verify the email before the save action: I check if the email is equal and, if it’s equal, I do unset to email field of my user object.
I hope I was useful.
Regards
Enrico Spanu
Medispa srl
Via San Calimero 1 - Milano
Viale Monastir 220 - Cagliari
medispa.it
my-icare.com
+39.02.39624490
Le informazioni contenute nella presente comunicazione e i relativi allegati possono essere riservate e sono, comunque, destinate esclusivamente alle persone o alla Società sopraindicati.
La diffusione, distribuzione e/o copiatura del documento trasmesso da parte di qualsiasi soggetto diverso dal destinatario è proibita, sia ai sensi dell’art. 616 c.p. , che ai sensi del D.Lgs. n. 196/2003 e successivi ravvedimenti.
Se avete ricevuto questo messaggio per errore, vi preghiamo di distruggerlo e di informarci immediatamente per telefono allo 02.39624490 o inviando un messaggio all’indirizzo e-mail info@medispa.it
…Sent from my iPhone
Il giorno 28 set 2017, alle ore 17:07, Junal Rahman ***@***.***> ha scritto:
@code-K @medispanu Having exact same issue for FB login. Did you find any solution?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
When I update a User object, the field verifiedEmail is forced to false even though setted to false
Steps to reproduce
verifyUserEmails: true,
emailVerifyTokenValidityDuration: 2 * 60 * 60, // in seconds (2 hours = 7200 seconds)
preventLoginWithUnverifiedEmail: true,
-It's not present any configuration r function in cloud main.js file
Update a existing user with parse node library
Expected Results
The value of emailVerified field must remain to old value
Actual Outcome
The value of emailVerified field changes to false value and verification email is sent.
Environment Setup
Server
Database
Logs/Trace
Include all relevant logs. You can turn on additional logging by configuring VERBOSE=1 in your environment.
The text was updated successfully, but these errors were encountered: