Closed dippynark closed 4 years ago
I'm a fool, the callback URL should be going to my application rather than directly to the authservice Deployment.
Fixed by changing https://authservice.<MY_DOMAIN>/oauth/callback
to https://grafana.<MY_DOMAIN>/oauth/callback
in my case
Glad you figured it out!
I have deployed the authservice very similarly to the Bookinfo example except I have deployed it as its own Deployment in its own Namespace with an EnvoyFilter configuring redirection for my application. I have therefore exposed authservice with a separate Gateway. I am using dex as my identity provider on the same cluster.
Most things seem to be working, however after signing into dex and getting redirected to the authservice callback (e.g. https://authservice./oauth/callback?code=y4df3ohtmbkpem7mvk2yrbkk4&state=c-e8G4sKuars0dWry2zixAtG_Ou9itd0PHPmrjyFJ4k) I am seeing
with the following in the authservice logs
My authservice config looks like:
I am using the following rather ugly command to generate the jwks field (potentially the mistake is there but I cannot see any):
Here's the raw response:
I am using the latest authservice image: v0.3.1