Skip to content

Implement AUTH for the management API - Master Story #305

@TessFerrandez

Description

@TessFerrandez

Description

As an Azure TRE administrator
I want to make sure that access is appropriately restricted to the management API
So that we don't have data leakage or unwanted templates/workspaces created

Acceptance critiera

  • Authentication/authorization is implemented with oauth2 and in such a way that AAD is replaceable (by writing a new auth component) to other auth providers in the future
  • Auth is done in this iteration with AAD - and through AAD Apps that have assigned users/roles
  • API access is restricted per the table below
  • Auth model is documented
Endpoint Access Comment
GET /workspaces Researcher/owner - assigned to the workspace - only the workspaces you belong to are returned. TRE Admin can see all
GET /workspaces/{workspace_id} Researcher/owner - assigned to the workspace TRE Admin can see all
POST /workspaces TRE Admin To create a workspace - the admin has to manually create an AAD app and provide it when creating the workspace
GET /workspacesTemplates TRE Admin
GET /worskpacesTemplates/{name} TRE Admin
POST /workspacesTemplates TRE Admin

Tasks - and sub stories

Metadata

Metadata

Labels

apiComposition Service APIauthAuthentication and authorizationsize/XLstoryStories are the smallest unit of work to be done for a project.

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions