-
Notifications
You must be signed in to change notification settings - Fork 113
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
allow for empty callback URL path #1049
Conversation
When configuring an empty path for the OIDC callback URL the used http MUX panics with "http: invalid pattern". This fix uses the MUX only for non-empty callback paths. If the path is empty the handler is directly used for the local http server without any MUX. Signed-off-by: Uwe Krueger <uwe.krueger@sap.com>
In what case is the callback URL empty? |
I wanted to use it with a local OIDC provider which was already configured with fixed callback URL for online scenario, We have changed it later, but basically it should work with an empty path, also. |
@bobcallaway What do you think about this? I’m not sure the use case, but it does clean up an error condition |
I'd prefer something like this (mostly b/c it has a test, and it will only listen on
|
@mandelsoft Would you like to update this PR to what Bob posted? |
Closing due to no activity, feel free to reopen |
Summary
When configuring an empty path for the OIDC callback URL the used http MUX panics with "http: invalid pattern".
This fix uses the MUX only for non-empty callback paths. If the path is empty the handler is directly used
for the local http server without any MUX.
Release Note
Support for OIDC callback URLs without path for usage of interactive mode
Documentation
Fixes: #1048