-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
Schema Registry tab erroring when using SASL_SSL #457
Comments
Hi abryant710! 👋 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. |
This is an infra issue, as our compose example works just fine. |
Further user feedback is requested. Please reply within 7 days or we might close the issue. |
@Haarolean I can see that you are using Please confirm before I provide a docker-compose example. |
Thanks for the additional feedback! We'll get back to your issue soon. |
Further user feedback is requested. Please reply within 7 days or we might close the issue. |
This was confirmed to work in a proper server deployment. Not working on localhost, likely for hostname inconsistency with certificates. Please close the ticket. |
Thanks for the additional feedback! We'll get back to your issue soon. |
Issue submitter TODO list
main
-labeled docker image and the issue still persists thereDescribe the bug (actual behavior)
I have set the following configuration setting in my Kafka UI container:
However, in the UI when I open the schema registry tab, I see the following error in the logs:
If I log into the Kafka UI container (after installing curl as root user) and try to curl the schema registry, it works fine:
Is there a configuration setting that I am missing in the Kafka UI container? Please help me resolve this issue.
Let me know if you need any more information.
Expected behavior
The Schema Registry tab should open and show all the schemas loaded into the Schema Registry, without any errors in the logs.
Your installation details
Docker compose project:
Services
Zookeeper
Image: confluentinc/cp-zookeeper:7.6.1.amd64
Restart Policy: unless-stopped
Environment Variables:
ZOOKEEPER_CLIENT_PORT: 2181
KAFKA_OPTS: Configured for SASL authentication and security.
Health Check: Uses nc to check if the Zookeeper port is open.
Kafka
Image: confluentinc/cp-enterprise-kafka:7.6.1.amd64
Restart Policy: unless-stopped
Environment Variables:
Configured for SASL_SSL communication with Zookeeper and clients.
SSL keystore and truststore locations and credentials are specified.
JAAS configuration for SASL authentication.
Exposed Ports: 9092
Health Check: Uses nc to check if the Kafka port is open.
Schema Registry
Image: confluentinc/cp-schema-registry:7.6.1.amd64
Restart Policy: unless-stopped
Environment Variables:
Configured for SASL_SSL communication with Kafka.
SSL keystore and truststore locations and credentials are specified.
JAAS configuration for SASL authentication.
Schema Registry listeners set to https://0.0.0.0:18085
Exposed Ports: 18085
Health Check: Uses curl to check if the Schema Registry is accessible over HTTPS.
Kafka-UI
Image: ghcr.io/kafbat/kafka-ui:latest
Restart Policy: unless-stopped
Environment Variables:
Configured for SASL_SSL communication with Kafka and Schema Registry.
SSL keystore and truststore locations and credentials are specified.
Schema Registry URL set to https://${KAFKA_UI_SCHEMA_REGISTRY_HOST}:18085
Exposed Ports: ${KAFKA_UI_PORT}
Health Check: Uses curl to check if the Kafka-UI is accessible.
Security Configuration
SASL_SSL: All Kafka-related services (Kafka broker, Schema Registry, Kafka-UI) are configured to use SASL_SSL for secure communication.
SSL Certificates: SSL keystore and truststore locations and credentials are specified for all services to ensure encrypted communication.
Health Checks
Health checks are configured for Zookeeper, Kafka, Schema Registry, and Kafka-UI to ensure that the services are running and accessible. These checks use nc and curl commands to verify service availability.
Steps to reproduce
Screenshots
No response
Logs
See description
Additional context
No response
The text was updated successfully, but these errors were encountered: