Skip to content
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

registrant verification on domain:delete does not function properly #1631

Closed
vohmar opened this issue Jul 3, 2020 · 1 comment · Fixed by #1638
Closed

registrant verification on domain:delete does not function properly #1631

vohmar opened this issue Jul 3, 2020 · 1 comment · Fixed by #1638
Assignees
Labels

Comments

@vohmar
Copy link
Contributor

vohmar commented Jul 3, 2020

Registrant verification is used with 2 domain operations - registrant change and delete. Both of these operations remove the rights of current registrant to the domain. If for example domain delete is executed confirmation email is sent to the domain registrant for him/her to confirm or reject the operation. If not done in time the default action is to reject the change.

In case of domain delete - pending delete status is set correctly and verification emails are sent out. But the change is accepted regardless of the registrant choice. both accept and reject result with a domain in pending delete state and out of the zone. Rejection should result with pre-confirmation state restored

@vohmar
Copy link
Contributor Author

vohmar commented Jul 9, 2020

It now appears that the effects of confirming and rejecting are flipped around so that accepting the change request results in rejection and rejecting it results with acceptance of the change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants