Access Token Invalide when userId is specific
🏬Self-hosted🪲Bugs🔗OIDC
When creating a user with a specific userId like this one : urn:ludocare:idp:user:de4af165-01ff-4997-92b6-50d3b9943acf.
Everything works well with the creation process.
Then, I can get back access token and refresh token.
However, when using the access token with userinfo, or with authenticated V1 API, zitadel says the access token is invalid.
Doing the same thing with a userId generated by zitadel is working well.
So I guess there is something wrong when checking the access token when the userId has some special chars lie ":"
Error in logs :
Token :
So I can't use the bearer token, But I can refresh it with the refresh token.
The new access token is still invalid.
Everything works well with the creation process.
Then, I can get back access token and refresh token.
However, when using the access token with userinfo, or with authenticated V1 API, zitadel says the access token is invalid.
Doing the same thing with a userId generated by zitadel is working well.
So I guess there is something wrong when checking the access token when the userId has some special chars lie ":"
Error in logs :
Token :
So I can't use the bearer token, But I can refresh it with the refresh token.
The new access token is still invalid.
