Hi,
We have detected that when an email modification is made and verified from the ARC console , the displayName field is not updated.
This situation causes a problem if the user then tries to register with the email prior to the change because a registration error appears, as if the email already existed when it does not.
It is necessary that when updating the email from the ARC console, the displayName field is updated with the new email.
You can see the documents with the problem in the ticket https://arcpublishing.atlassian.net/servicedesk/customer/portal/2/ACS-18061.
If you need any additional information please let me know
Thanks
Eva
Guest
Hi Ryan,
I understand what you are saying, but in our case there is a malfunction of the ARC console that is causing errors in subsequent registrations.
In this case we cannot touch anything on our part because the problem is in the ARC console. On the front end we have made the appropriate modifications to correct it, but we can't touch the ARC console code.
If it can not be corrected, what is the solution for users who do email change verification from the ARC console and then want to use the previous email for another registration? Because right now it gives an error and can not register and the only solution is to cancel the user data and that can lead us to lose customers.
Thanks
Hello
Thanks for this suggestion, I see the problem you're running into. Considering not all clients using the displayName in the same fashion, I don't think we'll be able to tackle this. Perhaps your websocket middleware could track and perform these updates?