Replies: 1 comment
-
|
This might be resolved by #1706 which fixes an issue that some nested routes don’t work well with oauth advertisement - hard to say though. As long as you configured your oauth app’s redirect correctly you shouldn’t have to add new routes |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This is my main mcp code:
And Google OAuth2 works correctly when ran locally.
But when I want to deploy it to internal k8s cluster which is hidden in VPN it doesn't work.
I have made
{api_base_url}/mcppublicly accessable and it didn't work, I tried exposing{api_base_url}/auth/callbackto public as well but it still doesn't work.Do I need any other endpoint exposed for OAuth Proxy to work?
Beta Was this translation helpful? Give feedback.
All reactions