unknown: crypto/aes: invalid key size 26 when adding new endpoint with access id/secret

[NiklasRosenstein]

If you are reporting a problem, please make sure the following information are provided:

Expected behavior and actual behavior:

Saving a new endpoint that uses credentials should succeed after the "Test Connection" was also successful.

Steps to reproduce the problem:

• Go to Administration > Registries
• Click + New Endpoint
• Select "Harbor" or "Docker Registry" as the Provider (behaviour for both is the same)
• Choose another Harbor instance for the Endpoint URL
• Set Access ID and Secret to a Robot account of the other Harbor instance
• Click Test Connection and note how it says "Connection tested successfully."
• Click Ok to save, but get a red box with "internal server error" instead.

Looking at harbor-core, the corresponding logs say:

2024-09-15T20:55:10Z [ERROR] [/lib/http/error.go:57]: {"errors":[{"code":"UNKNOWN","message":"unknown: crypto/aes: invalid key size 26"}]} 

I've found the following other issues but there was either no resolution or the suggested workaround did not work.

• Wrong encoding client_secret if it's long enough #15971
• New Registry Endpoint - Internal server error #15345
• Error with GCR configuration: invalid key size #14326
• Failed to create new registry endpoint #15146

The last one in particular suggests that the Access Secret cannot have a length greater than 16; but how am I supposed to replicate between two Harbor instances then when Robot account passwords are automatically generated and 32 characters in length?

Versions:

• harbor chart version: 1.15.1
• harbor version: 2.1.1

[NiklasRosenstein]

I managed to work around this by manually creating a new user (instead of a Robot account) with a password of 16 characters. This was complicated a bit further by the fact that by source instance was configured to use OIDC, and I couldn't find a way to create a new user as the UI would not allow me to (even after turning off that the OIDC method is the primary authentication method).

[stonezdj]

you need to check the /data/secret/secretkey, make sure it has the right length. or you remove this file and run install again.