-
Notifications
You must be signed in to change notification settings - Fork 5
Modify abilities to prevent link sharing #90
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
Modify abilities to prevent link sharing #90
Conversation
it 'returns forbidden response' do | ||
get "/api/projects/#{another_project.identifier}" | ||
|
||
expect(response).to have_http_status(:forbidden) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I'd rather this was :not_found
(no immediate information leakage about whether a project exists)
Timing attacks would still give it away though, as less work is (probably) being done if no project is found.
Happy for this to be pushed into a new issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interestingly, we now have separate design for these two cases, so maybe this is part of a wider discussion...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment about forbidden vs not found, but happy to merge
What's Changed?
ability
file to allow users to only read projects with nouser_id
(i.e. RPF starter/example projects) and projects owned by the userability_spec
testsshow_spec
tests to reflect the above changesimage_list
closes #89