This will mean that when the PTT is deployed in production, only authorised users can write/edit projects and their status entities in the ODA.
This reduces the risk of accidental or malicious damage to the software systems.
This will mean that when the PTT is deployed in production, only authorised users can write/edit projects and their status entities in the ODA.
This reduces the risk of accidental or malicious damage to the software systems.
Given that the OSO Data Archive (ODA) has access controls in place (See SP-4339), authorised users of the PTT can edit the states of projects and entities.
The PTT UI allows users to sign in, and then view, modify, and/or save status entities based on their role.
Complete permissions matrix required from ADR-34 outcomes for the PPT. 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 see their projects, but coarse grained groups who can r/w/x)
Demonstrate that user actions are logged (including who did the action)
Given that the OSO Data Archive (ODA) has access controls in place (See SP-4339 ), authorised users of the PTT can edit the states of projects and entities.
The PTT UI allows users to sign in, and then view, modify, and/or save status entities based on their role.
Complete permissions matrix required from ADR-34 outcomes for the PPT. 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 see their projects, but coarse grained groups who can r/w/x)
Demonstrate that user actions are logged (including who did the action)