You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 14, 2022. It is now read-only.
What?
In order to test certain functionality around constraining what users can see. It must be possible to have test accounts for the webapp with very specific experiment associations. It is quite easy to emulate an instrument scientist (Can view any experiment / run on an instrument they are associated with) however emulating a user may be more tricky.
This issue could potentially be done locally for development systems. But may require user office / ICAT involvement if we wish to have the same capabilities on production system. As such this issue should only cover development.
In addition to working out how to implement this, we should also create a script that creates these user accounts for us (this is important for automated testing in CI)
Where?
New scripts that create a user with specific permissions
How to test the issue is resolved
Run the user creation script and ensure that a new user has been added to the database
Ensure that the user has specific permissions to view only one instrument
Ensure a user can also be created that has specific permissions to only very certain experiments (this can be across varies instruments).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue raised by: [developer]
What?
In order to test certain functionality around constraining what users can see. It must be possible to have test accounts for the webapp with very specific experiment associations. It is quite easy to emulate an instrument scientist (Can view any experiment / run on an instrument they are associated with) however emulating a user may be more tricky.
This issue could potentially be done locally for development systems. But may require user office / ICAT involvement if we wish to have the same capabilities on production system. As such this issue should only cover development.
In addition to working out how to implement this, we should also create a script that creates these user accounts for us (this is important for automated testing in CI)
Where?
How to test the issue is resolved
The text was updated successfully, but these errors were encountered: