-
-
Notifications
You must be signed in to change notification settings - Fork 137
BE: Auth: Keystore support for OAuth2 #759
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
Comments
Hi alessio-bernesco! 👋 Welcome, and thank you for opening your first issue in the repo! Please wait for triaging by our maintainers. As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues. If you plan to raise a PR for this issue, please take a look at our contributing guide. |
As i test I tried to import the self signed certificate directly into the main trust store, loggin as root into the running docker:
and then:
This way everything works fine, so the cert itself seems correct. Also as a test changing the custom truststore location or password, using non valid locations/password the startup fails, so the truststore is located and validated at startup. |
same issue: |
Most likely,
|
Issue submitter TODO list
main
-labeled docker image and the issue still persists thereDescribe the bug (actual behavior)
Hello,
i've added to the config file this:
and mounted a volume with the truststore i'm still unable to start the docker image.
The related error is:
The certificate added to the truststore is a self signed certificate, the same used to add https connection to KeyCloak.
How can i provide more insights?
Thanks,
Alessio
Expected behavior
No response
Your installation details
docker ghcr.io/kafbat/kafka-ui:latest
Steps to reproduce
create a folder with a custom truststore
mount the folder inside the docker at /etc/certs
modify the config.yaml file to use the custom truststore
Screenshots
No response
Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: