You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In certain situation public/private key is not allowed for security reasons due to lack of rotation. In those cases authentication against cloud environments is performed via auth-agents. On AWS the agent creates a credential file that is renewed periodically. I have checked the core implementation of cvat and the API for cloud storage supports the keys contained in the credentials file accesskey, secretkey and token but ui does not allow to introduce those parameters or environment variables containing those parameters.
Describe the solution you'd like
Is it possible to support credential file path ingest to authenticate AWS bucket? That would add greater security measures and allow more users as the public/private keys are starting to be considered less secure by regulations :(
Describe alternatives you've considered
Full cloud host for server and storage in same VPC is other option but the budget is too expensive for my capabilities
Additional context
No response
The text was updated successfully, but these errors were encountered:
Actions before raising this issue
Is your feature request related to a problem? Please describe.
In certain situation public/private key is not allowed for security reasons due to lack of rotation. In those cases authentication against cloud environments is performed via auth-agents. On AWS the agent creates a credential file that is renewed periodically. I have checked the core implementation of cvat and the API for cloud storage supports the keys contained in the credentials file accesskey, secretkey and token but ui does not allow to introduce those parameters or environment variables containing those parameters.
Describe the solution you'd like
Is it possible to support credential file path ingest to authenticate AWS bucket? That would add greater security measures and allow more users as the public/private keys are starting to be considered less secure by regulations :(
Describe alternatives you've considered
Full cloud host for server and storage in same VPC is other option but the budget is too expensive for my capabilities
Additional context
No response
The text was updated successfully, but these errors were encountered: