Specify username/password for apicurio registry #23349
-
I'm trying to follow the Using Apache Kafka with Schema Registry and Avro guide. How do I connect to a schema registry that requires authentication? I see there is a I see how I might do the configuration when I'm manually creating a producer/consumer, but not sure how I would get that information into the producer/consumer that Quarkus creates. I'm trying to connect my app to the Red Hat managed service offering. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 15 replies
-
@carlesarnal How is are the credential passed to the serde? Are there specific attributes? |
Beta Was this translation helpful? Give feedback.
-
Hi, Yes, there's a set of configuration properties used for auth. For oauth you must use the following properties:
And for basic auth the following ones:
As a minor note, if you're using Red Hat managed version of Service Registry and want to use basic auth (although there's no reason to do so) you must use the client id and client secret of your service account as the username password pair. |
Beta Was this translation helpful? Give feedback.
Hi,
Yes, there's a set of configuration properties used for auth. For oauth you must use the following properties:
mp.messaging.connector.smallrye-kafka.apicurio.auth.service.token.endpoint
mp.messaging.connector.smallrye-kafka.apicurio.auth.client.id
mp.messaging.connector.smallrye-kafka.apicurio.auth.client.secret
And for basic auth the following ones:
mp.messaging.connector.smallrye-kafka.apicurio.auth.username
mp.messaging.connector.smallrye-kafka.apicurio.auth.password
As a minor note, if you're using Red Hat managed version of Service Registry and want to use basic auth (although there's no reason to do so) you must use the client id and client secret of your service account as the …