From cdcee6dff37dac6b381c63bfd8746f9db58a507e Mon Sep 17 00:00:00 2001 From: Alex Kanitz Date: Wed, 4 Oct 2023 01:33:09 -0700 Subject: [PATCH] auth: update AuthN/AuthZ documentation --- openapi/task_execution_service.openapi.yaml | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/openapi/task_execution_service.openapi.yaml b/openapi/task_execution_service.openapi.yaml index d70bf2f..e280187 100644 --- a/openapi/task_execution_service.openapi.yaml +++ b/openapi/task_execution_service.openapi.yaml @@ -49,14 +49,12 @@ info: ### Authentication and Authorization - Is is envisaged that most TES API instances will require users to authenticate to use the endpoints. - However, the decision if authentication is required should be taken by TES API implementers. + Implementers are required to implement the authentication schemes defined in + `components.securitySchemes`, but they are free to define and implement + additional schemes as per their requirements. - - If authentication is required, we recommend that TES implementations use an OAuth2 bearer token, although they can choose other mechanisms if appropriate. - - - Checking that a user is authorized to submit TES requests is a responsibility of TES implementations. + Checking that a user is authorized to submit TES requests is the responsibility + of each implementation. ### CORS