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

Removing registry lock should not remove statuses set prior to setting it #1900

Closed
vohmar opened this issue Apr 1, 2021 · 0 comments · Fixed by #1902
Closed

Removing registry lock should not remove statuses set prior to setting it #1900

vohmar opened this issue Apr 1, 2021 · 0 comments · Fixed by #1902
Assignees

Comments

@vohmar
Copy link
Contributor

vohmar commented Apr 1, 2021

Registry lock sets 3 restrictive statuses to a domain - serverUpdateProhibited, serverTransferProhibited, serverDeleteProhibited. Unlocking a domain removes those same 3 statuses even if some of them were set on a domain prior setting the registry lock thus creating a method for registrants to remove administratively set restrictions.

Removing registry lock should affect only those statuses that were actually set on locking the domain

there is one potentially tricky scenario to handle here. Registry Lock is effective only in the presence of all three restrictive statuses. If any of them is removed by admin the domain is not considered locked any more and registrant is once again able to lock it. But in this case statuses to be removed on unlocking are the statuses set by last and prior locking actions.

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

Successfully merging a pull request may close this issue.

2 participants