-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Bug]: OAuth endpoints with custom CA no longer working #11082
Comments
I guess you should start by providing a full configuration and log files. |
config:
mount paths:
logs:
|
Please share the full logs and full configurations? These things matter, and there is a reason we ask for them. If you know that these two snippets are all that is needed to figure things out, you might understand it better than we do and in that case please open a PR with the fix. |
Sorry I understand I just don't have full access any more and I was wondering if any of this make sense, otherwise I will share the full logs and configuration once I've tested this again and can share what is required. |
Bug Description
After upgrading to 0.45 we are suddenly seeing the following error:
when trying to set up an OAuth endpoint with custom CA via
tlsTrustedCertificates
config.According to the
strimzi-kafka-oauth
documentation both truststores and PEM certs are supported and this previously worked with a simple k8s Secret storing a CA in .pem format. Is there a reason it suddenly expects a truststore to be provided? I couldn't find anything in the Configuring Strimzi docs that explains this change.Steps to reproduce
No response
Expected behavior
No response
Strimzi version
0.45
Kubernetes version
1.28
Installation method
No response
Infrastructure
No response
Configuration files and logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: