Allow longer S3 Access Key and Secret Key

[sebagarayco]

My actions before raising this issue

• Read/searched the docs
• Searched past issues

Expected Behaviour

I would like to connect to an AWS S3 compatble service (Cloud Storage) served from an on-premise storage.

Current Behaviour

Both AccessKey and SecretKey fields are truncated to match AWS's number of characters.

Our AWS S3 compatible service uses 129 character long AccessKey and SecretKey.

Possible Solution

Modify Acces Key and Secret Key fields to allow entering 129 characters long keys.

Steps to Reproduce (for bugs)

1. Click on Cloud Storage
2. Click on Add (+)
3. Enter Bucket Name, Endpoint, Access Key and Secret Key (both are truncated)

Context

Your Environment

• Git hash commit (git log -1):
• Docker version docker version (e.g. Docker 17.0.05): Version: 20.10.12
• Are you using Docker Swarm or Kubernetes? No
• Operating System and version (e.g. Linux, Windows, MacOS): macOS 12.0.1
• Other diagnostic information / logs:
  Logs from `cvat` container

  [Wed Apr 20 22:39:10.737344 2022] [wsgi:error] [pid 555:tid 275483744000] [remote 172.20.0.4:35558] ERROR - 2022-04-20 22:39:10,735 - serializers - Cannot create resource datacenter with specified credentials. Access forbidden.

Next steps

You may join our Gitter channel for community support.

[nmanovic]

@sebagarayco , thanks for the report. Could you please contribute and send us a PR with necessary changes? It should not be a complex change.

[sebagarayco]

Done @nmanovic, thanks for the tip!