-
Notifications
You must be signed in to change notification settings - Fork 9
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
[BUG] Unintended Access to dRep Registration and Editing Functions #1183
Comments
That should already be fixed @pmbinapps could you please retest it making sure that the issue no longer exists? |
OK NOW
@m-i-k-e TBC any behaviour mentioned in Expected results should be implemented. |
Hello @pmbinapps , The Impact
|
Sentry Issue Details
Test Report
|
@pmbinapps any updates on this? |
@kneerose assigning to @MSzalowski to clarify how to handle /register_drep when user is already a DRep. |
@jdyczka any update on this? |
@kneerose Yes, the same problem exists for retire_drep, register_direct_voter and retire_direct_voter. |
…r-actions [#1183] Restrict access for registration and retirement routes
@jdyczka @MSzalowski Is this now deployed? |
I see this message while navigating to the /register_drep page when the user is already a DRep. It seems that the issue has been fixed. What do you think, @MSzalowski and @jdyczka ? CC: @bosko-m |
Closing as per the comment above. |
Context & versions
/register_drep
page, intended for new dRep registrations./edit_drep
page, meant for modifying existing dRep profiles.Steps to reproduce
dRep user:
/register_drep
.Non dRep User:
/edit_drep
.Expected behaviour
/register_drep
, a registered dRep should be redirected to a relevant page (e.g. dashboard) with a clear message indicating they are already registered./edit_drep
, they should be redirected to the registration page (/register_drep) with a message explaining they need to register first.Allure Report references
The text was updated successfully, but these errors were encountered: