Access Restriction Behaviour inconsistent

[tognotti]

Bug report

Bug description

When a user is not allowed to read, create or update a field, the field is still shown in Admin UI with a shield next to it. When a user is not allowed to create items of a list the create button is still shown to the user. If a user is not able to read a list, the list is still shown to the user in the left navigation.

To Reproduce

Steps to reproduce the behaviour. Please provide code snippets or a repository:

1. Create keystonejs App and use the starter template
2. Create a user which is no admin
3. Got to Admin UI
4. Go to Users
5. Click on the new user
6. Field "isAdmin" is presented to the user and the user can edit it and only get an error when trying to save

Expected behaviour

Fields users are not allowed to read, create and update should not be shown in Admin UI and fields users are not allowed to update or create but are allowed to read should be disabled. Lists users are not allowed to read should be removed from the sidebar and if users can not create items the create buttons should not be shown at all. This works as expected with static access control

System information

• OS: macOS

[matheuschimelli]

Have you enabled the auth protection for the Admin UI?

[tognotti]

Have you enabled the auth protection for the Admin UI?

Of course I have. It already happens in the starter project. The fields are displayed and only when trying to update them an error occurs instead of them being disabled or not shown at all if the user also is not allowed to read them.

[tognotti]

This is what happens if auth is set up like in the starter app. If a user is not allowed to read a list, it still is shown in the sidebar navigation. If a user has no access to a field, it is still shown to the user but updating it will fail. There is a shield next to a field if a user can not update it.

[stale]

It looks like there hasn't been any activity here in over 6 months. Sorry about that! We've flagged this issue for special attention. It wil be manually reviewed by maintainers, not automatically closed. If you have any additional information please leave us a comment. It really helps! Thank you for you contribution. :)

[bladey]

Keystone 5 has officially moved into active maintenance mode as we push towards the next major new version Keystone Next, you can find out more information about this transition here.

In an effort to sustain the project going forward, we're cleaning up and closing old issues such as this one. If you feel this issue is still relevant for Keystone Next, please let us know.