Replies: 1 comment 4 replies
-
Hi @rltbg CallbackUri: "/secure/oidc/callback" Constraining the session cookie to SessionCookie:
Path: "/secure" |
Beta Was this translation helpful? Give feedback.
4 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.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi! I was looking through the documentation here and I had a question regarding the callback configuration while securing a sub route.
Would it be possible to support a CallbackUri that can be set under a specific sub-route, so that the redirect and subsequent return stay within that sub-route?
For example, let’s say I want to secure the route /secure, which hosts a complete application. Ideally, the callback could then be /secure/oidc/callback instead of /oidc/callback. This way, after authentication, I’d be redirected back into /secure directly, without affecting other routes.
The main benefit would be in cases where multiple apps are hosted on different sub-routes (e.g. /secure, /dashboard, etc.), allowing each one to handle its own callback in isolation, without interfering with the others.
I’ve already tried a Kubernetes configuration following that idea:
However, when I test this setup, the login flow ends with a 502 error, and I never get redirected back into the app. This makes me think that handling callbacks under sub-routes is not (yet) supported by the plugin.
Would this be something possible to implement, or is there a limitation preventing it?
Beta Was this translation helpful? Give feedback.
All reactions