Skip to content

/collection/{slug}/estimation: admin should have access to everyone's estimation page #889

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

Closed
0pdd opened this issue Jun 21, 2018 · 1 comment
Assignees
Milestone

Comments

@0pdd
Copy link

0pdd commented Jun 21, 2018

The puzzle 884-61920ac4 from #884 has to be resolved:

// @todo #884 /collection/{slug}/estimation: only owner should have access to estimation page

The puzzle was created by Slava Semushin on 20-Jun-18.

@0pdd 0pdd added the techdebt label Jun 21, 2018
@php-coder php-coder added this to the 0.4 milestone Jun 21, 2018
@php-coder php-coder self-assigned this May 25, 2019
@php-coder php-coder pinned this issue Jun 3, 2019
@php-coder php-coder changed the title /collection/{slug}/estimation: only owner should have access to estimation page /collection/{slug}/estimation: admin should have access to everyone's estimation page Jun 15, 2019
@php-coder
Copy link
Owner

At this moment the task is already solved: "only owner should have access to estimation page" statement is true because in #891 we restricted the access to the service method by only collection's owner. Even if the access on the page-level aren't so strict, the page can't be opened anyway because the service method has a stricter protection. See spring-projects/spring-security#6948 for details.

But the access still needs to be altered to allow admin access to everyone's page. This should simplify debug when it will be required. So, I've edited the issue's title to reflect that.

php-coder added a commit that referenced this issue Jun 15, 2019
Correction for d429810 commit.

Addressed to #889

No functional changes.

[skip ci]
@php-coder php-coder unpinned this issue Jun 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants