-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Unable to skip basic authentication for specified paths in ksqldb-server #9206
Comments
@alapidas , this seems to be control plane stuff, can you take this? |
I was able to confirm the bug, working on a patch now. |
@agavra do you expect that this will be included in the ksqldb 0.28 release? |
yes, this should be part of the 0.28 release :) |
Has anyone managed to get this working on version 0.28.2? The change has been merged but I still cant skip |
Not working for me either - trying to use the same skip paths configuration as seen here: |
Same here. It appears that the config is loaded but ignored. Here's the relevant log snippet
Has this anything to do with the internal listener address? |
hey @agavra , possible to reopen this? |
yeah I'll reopen this - cc @suhas-satish @alapidas |
I was able to reproduce the bug on master, and yes, the parameter is completely ignored for basic auth. I will implement a fix. |
Describe the bug
Use of the config option
authentication.skip.paths
does not actually allow the specified paths to skip basic authentication for ksqldb-server.To Reproduce
Steps to reproduce the behavior, include:
cp-all-in-one-community
directory undocker-compose -f docker-compose.yml -f docker-compose.ksqldb-server-basic-auth.yml up -d
docker-compose.ksqldb-server-basic-auth.yml
override file basic auth is configured for ksqldb-server along with/healthcheck
defined in theauthentication.skip.paths
option.Expected behavior
The command
curl localhost:8088/healthcheck
with no basic auth provided returns the health check informationActual behavior
The command
curl localhost:8088/healthcheck
returns an HTTP 401Additional context
I expect there is additional configuration that I am missing here, but so far I have not found what it could be.
The text was updated successfully, but these errors were encountered: