failed to validate token error="failed to parse ApiKey: legacy prefix length mismatch"

[wenco]

Description

Yes. When testing Headscale v0.28.0-beta.1 together with Headplane v0.6.2-beta.3, the OIDC provider used was prdexidp/dex:v2.44.0.
The OIDC login flow itself completes successfully and the callback is received correctly; however, after the callback, the page is redirected back to the login page, resulting in a login loop. At the same time, the Headscale log console reports the following error:
failed to validate token error="failed to parse ApiKey: legacy prefix length mismatch" client_address=...
Therefore, I am currently unable to determine whether this issue is a bug in Headscale or in Headplane.
thx

Headplane Version

v0.6.2-beta.3

Headscale Version

v0.28.0-beta.1

[Shaxine]

I'm having the same error trying to connect only using the API Key (without using OIDC).

It seems that HS v0.28.0-beta.1 changed the API Keys' logic, and my API Key was old and had a prefix (first chars until the .) of size 10 instead of 7. When calling the API directly (curl -H "Authorization: Bearer <API_KEY>" https://headscale.example.com/api/v1/user) I was getting: Unauthorized

I generated a new key (with the new format hskey-api-{prefix}-{secret}) and I can call the API directly, but HP now presents the following error: API key was not found in the Headscale database