FYou mind sharing your settings?
Maybe I can spot the issue
Maybe I can spot the issue
Fthat could be an issue, yes.
FCan you share the URL from your browser when you see the error from zitadel?
There embeded is the redirect uri your grafana sends to zitadel.
There embeded is the redirect uri your grafana sends to zitadel.
FFOk but your grafana sent the above to zitadel
FIt looks like @loulz0r said that you need to set the root_url
FI see
Fyou need to append the path as well
F
FThe siging key pair is only zitadel telling you that it created a key pair to sign tokens. This has nothing todo with TLS stuff.
To me it looks like you need to tell your grafana the CA you are using (or you need to use trusted certificates)
To me it looks like you need to tell your grafana the CA you are using (or you need to use trusted certificates)
FFI am not sure why grafan tries to call that 
Fuserinfo exist though since that is where a client can check a token
FI just looked at your scope... try adding 'email' there
FGreat nice to hear
L
Lanyone here knows a fix for that? here is a screenshot of my settings
L
L
D@Lasse you need to check your "Redirect Settings" inside your grafana Application settings (which should be inside your grafana Project) in the Zitadel console. In my case I have a grafana project, which in turn has a grafana PKCE application. You likely forgot to configure a redirect URI which will need to be something akin to https://your.grafana.url/login/generic_oauth
Lfixed it yesterday, forgot to write it here. that as also the fix for me
but thanks
but thanks