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

#1534 Change config permission to 'administer site configuration' #780

Merged
merged 1 commit into from
Jun 24, 2020
Merged

#1534 Change config permission to 'administer site configuration' #780

merged 1 commit into from
Jun 24, 2020

Conversation

kayakr
Copy link

@kayakr kayakr commented Jun 3, 2020

Github Ticket:
#1534 Tighten access to Islandora IIIF config form
Islandora/documentation#1534

What does this Pull Request do?

Changes config permission for Islandora IIIF config form from 'access administration pages' to 'administer site configuration' so that some roles can have (say) content administration via administration pages without being able to alter key site configuration.

A brief description of what the intended result of the PR will be and/or what problem it solves.

What's new?

Changed permission for /admin/config/islandora/iiif

How should this be tested?

With a user role with 'access administration pages' permission note that /admin/config/islandora/iiif is accessible. With this patch they should get "You are not authorised to access this page.", and 'administer site configuration' is required instead.

Interested parties

@Islandora/8-x-committers

@manez
Copy link
Member

manez commented Jun 18, 2020

This is probably me not understanding something simple, but I can't find the permission "access administration pages" to test this out. Is it the same as "Use the administration pages and help?"

@kayakr
Copy link
Author

kayakr commented Jun 18, 2020

@manez That's the correct permission: "Use the administration pages and help" is the title used for the table row at /admin/people/permissions but access administration pages is the permission string used in code.

@DonRichards
Copy link
Member

@kayakr to get a faster response to a PR it helps to make the "How to test" as approachable as possible. Something I find highly useful is to include step by step instructions with screen shots (if needed) to basically walk a noobie/newby through the process of seeing the original result, pull in the change, verify the change worked and any other thing they should check to approve the PR. I'd do this but I'm not completely sure what to test and I have a very limited time window of open time.

@manez manez self-requested a review June 24, 2020 17:24
@manez
Copy link
Member

manez commented Jun 24, 2020

Tested and it all seems to work as advertised. My user with "Use the administration pages and help" permissions could access /admin/config/islandora/iiif before the PR, and can't afterwards.

Copy link
Member

@manez manez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs @Islandora/8-x-committers to finalize, but tested and it works!

@dannylamb
Copy link

Happy to merge based on your approval @manez

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

Successfully merging this pull request may close these issues.

4 participants