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

JMX with enabled authentication does not work on FIPS enabled Kubernetes clusters #9952

Open
scholzj opened this issue Apr 11, 2024 · 1 comment

Comments

@scholzj
Copy link
Member

scholzj commented Apr 11, 2024

When running under FIPS mode, our JMX support currently seems to work fine when authentication is disabled. But when you enable it, the clients seem to fail the authentication. This should be further investigated.

This relates to the system test JmxIsolatedST.testKafkaZookeeperAndKafkaConnectWithJMX.

@scholzj
Copy link
Member Author

scholzj commented May 2, 2024

Triaged on the community call on 2.5.2024: This should be tracked and ideally fixed. It needs to be figured out what the problem is in the first place as the only information we have right now is that JMX does not work under FIPS with authentication enabled.

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

No branches or pull requests

1 participant