Closed danielr1996 closed 3 months ago
After testing a few of these endpoints with curl I noticed that I also get the error Error: unknown_error, Description: For more on this error consult the server log at the debug level.
directly from keycloak, so this seems to a problem on my side.
I got It working now, my keycloak was misconfigured, I needed to set the access type to public instead of confidential.
To answer some of your questions:
What is the domain hint?
It's a Bitwarden parameter that is unused. During the normal flow you should not see it (a dummy value is set after you input your email).
What also confused me is the fact that all the oidc calls seem to go to an internal endpoint
identity/connect/authorize
You are redirected to identity/connect/authorize
which then redirect to the correct url depending on the client (web
, mobile
or desktop
).
There is no additional oidc server, but the tokens sent by Key cloak are wrapped in another JWT to be able to carry more information.
When clicking the "login with sso provider" button I get redirected to keycloak and can login, however back at vaultwarden I get the error:
Failed to contact token endpoint: ServerResponse(StandardErrorResponse { error: unknown_error, error_description: Some("For more on this error consult the server log at the debug level."), error_uri: None })
.Here's the log
What is the domain hint? should this be the real domain of either the oidc endpoint or the vaultwarden instance
[request][INFO] GET /identity/sso/prevalidate?domainHint=VaultWarden
[request][INFO] GET /identity/connect/authorize?client_id=web&redirect_uri=htt
[request][INFO] GET /sso-connector.html?code=eyJ0eXAiOiJKV1QiLCJhbGciO