Skip to content
This repository has been archived by the owner on Feb 13, 2019. It is now read-only.

Better handling for access issues #50

Open
nathanperkins opened this issue Jul 10, 2016 · 1 comment
Open

Better handling for access issues #50

nathanperkins opened this issue Jul 10, 2016 · 1 comment

Comments

@nathanperkins
Copy link

nathanperkins commented Jul 10, 2016

Issue
When logged in as a restricted user, trying to open some restricted pages will give a generic error or Internal Server Error (500). Messaging could be improved by returning a page that states the current user is in a group that does not have access to the resource.

How to replicate

  1. Attempt to login as a user that has no access.
    or
  2. Create a support user in the ACLs and login as that user.
  3. Attempt to access the ACL page.
@nathanperkins
Copy link
Author

nathanperkins commented Jul 10, 2016

Sometimes, I see an access denied message, so it's not consistent.

For an example, I'm logged in as a user that no longer has access and I'm getting an internal server error (500), with no option to logout. I have to clear my browser cookies to get back in.

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

No branches or pull requests

1 participant