There should be support for multiple ways of securing resource manager upload and copy functionality, there should also be a way to secure presign and get endpoints but this should be separated from upload.
Security methods
Security type is defined in profile
Currently there is a goal to support at least two types
Basic auth - request should come with user:pass in Authentication header. This credentials should be loaded from BASIC_AUTH_CREDENTIALS environment variable.
Api keys - request come with Authorization: Api {api_key}. This credentials should be loaded from API_CREDENTIALS list of keys separated by ,
Presigning
When using AWS S3 for downloading presigning is already handled by S3 itself, to add support for this on local storage this should be implemented with a jwt token.
Token should contain:
path to file
expiration
This should be appended to get endpoint as token={jwt_token}query param
### Description
There should be support for multiple ways of securing resource manager upload and copy functionality, there should also be a way to secure presign and get endpoints but this should be separated from upload.
### Security methods
Security type is defined in profile
Currently there is a goal to support at least two types
Basic auth - request should come with user:pass in Authentication header. This credentials should be loaded from BASIC_AUTH_CREDENTIALS environment variable.
Api keys - request come with `Authorization: Api {api_key}`. This credentials should be loaded from API_CREDENTIALS list of keys separated by `,`
#### Presigning
When using AWS S3 for downloading presigning is already handled by S3 itself, to add support for this on local storage this should be implemented with a jwt token.
Token should contain:
* path to file
* expiration
This should be appended to get endpoint as `token={jwt_token}`query param
brajkovic
self-assigned this 2021-11-19 17:56:57 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Description
There should be support for multiple ways of securing resource manager upload and copy functionality, there should also be a way to secure presign and get endpoints but this should be separated from upload.
Security methods
Security type is defined in profile
Currently there is a goal to support at least two types
Basic auth - request should come with user:pass in Authentication header. This credentials should be loaded from BASIC_AUTH_CREDENTIALS environment variable.
Api keys - request come with
Authorization: Api {api_key}. This credentials should be loaded from API_CREDENTIALS list of keys separated by,Presigning
When using AWS S3 for downloading presigning is already handled by S3 itself, to add support for this on local storage this should be implemented with a jwt token.
Token should contain:
This should be appended to get endpoint as
token={jwt_token}query param