-
Notifications
You must be signed in to change notification settings - Fork 26
User's emails should not be updated without verification #62
Comments
For now, can we just disable the field? |
Sure we can. @burrsitis do you think it's better not to allow to change the email at all until we start verifying emails? |
I would think so. We don't want users changing to fake email addresses. |
Later on we should think about some sync between RHD and OSIO accounts (names, emails, etc). |
So a lower priority task should be that - Edit: Or maybe should be done together in the same PR so as to not introduce a hole. |
We should sync. But use Auth as the source of truth. We should update KC user based on what we have in Auth. We have to update because we need updated info in the token.
|
Understood, so we change the direction of sync! :) |
A caller can add custom variables that get rendered as part of the notification as well as add Notification Type level validators of request data. Request data.attributes.custom.* is made available to the template. Include basic mail template for fabric8-auth email verification support. Related to fabric8-services/fabric8-auth#62
When user updates email address, an email with verification URL is sent to the email. fixes #62
Currently users can change email without verification
The text was updated successfully, but these errors were encountered: