Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[question] single redirect_uri_path for multiple upstream services #118

Open
illyaMs opened this issue Apr 5, 2019 · 2 comments
Open

[question] single redirect_uri_path for multiple upstream services #118

illyaMs opened this issue Apr 5, 2019 · 2 comments

Comments

@illyaMs
Copy link

illyaMs commented Apr 5, 2019

Hi there (and thanks for the great work).

I'm trying to protect several internal k8s services by exposing appropriate kong services with current plugin being activated. Google is used as an OIDC provider.

The problem I face is with setting the proper redirect_uri_path value in plugin settings. Since we're forced to add the whitelist of Authorized redirect URIs on google side, it seems like I have to add there all the kong routes paths for all the services I'm trying to protect. This doesn't look like a scale-able solution though, I would rather add any single trusted endpoint pointing to kong \ kong-oidc and let the plugin or kong itself redirect further to a service that was initially requested.

The question is: is it possible via current plugin? Maybe chaining it with some other plugin/tool for certain kong services/routes would make the job done? Thanks in advance.

@illyaMs illyaMs changed the title [question] redirect_uri_path for multiple upstream services [question] single redirect_uri_path for multiple upstream services Apr 5, 2019
@sathishkumar-p
Copy link

Able to find solution ?

@illyaMs
Copy link
Author

illyaMs commented Sep 13, 2023

no, don't remember the details now, but I didn't proceed with that idea in the end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants