This will mean that when the OET is deployed in production, only authorised users can read and modify the underlying ODA database, or execute commands on the telescope
This will mean that when the OET is deployed in production, only authorised users can read and modify the underlying ODA database, or execute commands on the telescope
The OET allows a user to authenticate, and then correctly validates tokens which it then uses with the ODA to ensure that the user can only see/alter those things which they are authorised to do.
An authenticated OET user with the correct permissions can send commands to the telescope for execution.
Complete permissions matrix required from ADR-34 outcomes for the OET. Keeping things simplistic to start with in alignment with OIDC standards. (i.e don't worry about commissioning scientists being the only ones able to be able to execute their projects, but coarse grained groups who can r/w/x)
Demonstrate that user actions are logged (including who did the action)
The OET allows a user to authenticate, and then correctly validates tokens which it then uses with the ODA to ensure that the user can only see/alter those things which they are authorised to do.
An authenticated OET user with the correct permissions can send commands to the telescope for execution.
Complete permissions matrix required from ADR-34 outcomes for the OET. Keeping things simplistic to start with in alignment with OIDC standards. (i.e don't worry about commissioning scientists being the only ones able to be able to execute their projects, but coarse grained groups who can r/w/x)
Demonstrate that user actions are logged (including who did the action)