-
Notifications
You must be signed in to change notification settings - Fork 71
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 setup authentication for schema-registry #646
Comments
You need to add Hope this help. Please let me know if something is unclear on the documentation. |
Just to get this correctly, I am writing down the steps to be performed: Step 1: I need to create a hashed secret using the command Step 2: Create an authfile.json having the user credentials and authorization in it.
Step 3: Pass the file path of authfile.json in environment variable Do we need to enable any additional flags in addition to the above configuration mentioned above? |
You're correct here. If However please note that REST API is separate in case you are running both Schema Registry and Kafka REST API in same Karapace instance. |
Thank you for you help earlier, I am able to setup the BASIC authentication on I was attempting to understand your last statement and, in light of that, I was attempting to determine what it meant to have both the karapace_rest and karapace_registry options set to true. Then I understood that it meant I was using the same Karapace instance to run both the Kafka REST API and the Schema Registry. What do you mean by REST API being separate, based on your previous comment? Also, I tried to create a schema using this curl To which I am getting a successful response. But, when I am trying to execute the below curl given in karapace documentation Produce a message backed up by schema registry:
Response: Also, I am getting below error in stacktrace:
Could you please explain why this problem is occurring? |
Hi @tvainika , do you have any update on the above issue ? |
Karapace is able to run both Kafka REST API and schema registry in same process. Internally, for authentication and other reasons, it will make REST calls from REST component to schema registry. Based on your stack trace it seems there something fails, but I was not able to reproduce this way. It should not get internal server errors. Can you share more details about this setup and Karapace version? In my testing I received 400 based error codes if my configuration did not allow REST component to access the schema registry. |
What specific settings must I make in order to enable basic authentication so that I may access the Karapace Schema Registry?
I can currently create schemas using the curl code below with or without a password. It appears to be a configuration issue.
Please outline the specific processes for me. My objective is to prohibit unauthorised access to this endpoint at https://localhost:8081.
And after the authentication is enabled, I assume the curl to create schema should look something like below :
or may be I should pass some auth headers to create schema
The text was updated successfully, but these errors were encountered: