@@ -49,3 +49,7 @@ Discussions with various Module Owners and CSP is in progress and below requirem
<h4>g. Information Security</h4>
Below are some of the user stories captured as part of login and initial admin tasks:
<ul><li>System Administrator</li><li><ul><li>User should be able to login as a system administrator Check for the roles will be done by E&O roles/groups API</li><li>User should be able to configure the OSDU user authentication system to use my company’s IDP. As part of initial setup, an IDP will be configured for authentication of Admin App</li><li>User should be able to set up the authentication system for Single Sign On for users – This will be during initial setup itself</li><li>User should be able to be able to assign roles of the OSDU users – E&O APIs will be called for these operations</li></ul></li><li>System Administrator (roles assignments, system configurations)</li><li><ul><li>System Operator (system monitoring, reporting, dashboarding, etc) – To be discussed and reviewed with what all APIs are available</li><li>Data Manager (Data Loading, ingestion, E&O policy management) To be discussed and reviewed with what all APIs are available</li></ul></li><li>Users (login)</li><li><ul><li>User should be able to configure access to the external data sources (EDS) As part of initial setup, an IDP will be configured for authentication of Admin App</li><li>User should be able to configure the system behaviours (e.g., the visibility of metadata if the actual data is protected) As long as the APIs are available to update the system behaviours, this should be possible</li></ul></li><li>System Operator (Comments as above)</li><li><ul><li>User should be able to login as a system operator</li><li>User should be able to able to run all system audit and operation reporting services</li><li>User should be able to configure the system dashboard</li><li>User should be able to run the system reporting services and create the dashboard</li></ul></li><li>Data Manager (Comments as above)</li><li><ul><li>User should be able to load and ingest data with manifests</li><li>User should be able to load and ingest data without manifests</li><li>User should be able to load and ingest master data</li><li>User should be able to load and ingest reference data</li><li>User should be able to load and ingest quality rules</li><li>User should be able to see a list of all currently-running ingestion jobs with their current status</li><li>User should be able to see a history of recent (for some definition of recent) ingestion jobs, with their status (and maybe size, number of objects, error log, etc.)</li><li>User should be able to kill/cancel a currently-running ingestion job</li></ul></li><li>End Users (Comments as above)</li><li><ul><li>User should be able to login as an end user</li><li>User should be able to be able to search for availability of data</li><li>User should be able to access the application and service catalog of the Marketing Site</li><li>User should be able to be able to purchase the application or service</li><li>Once I purchase the application or service, they will appear on the application of service pages</li><li>User should be able to execute an application or service which I purchase</li><li>User should be able to list all purchased data sets</li></ul></li></ul>
<h4>h. Audit and Metrics (system monitoring)</h4>
To be updated
<h2>3. Design & Development Approach</h2>
Below is the high-level understanding based on various discussions with stakeholders till now.
