You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Adding Security page, the protocol mentioned in the example is amqp however the following text reads
The example above shows how to specify that your server (a Kafka broker) requires a user and a password to establish a connection.
The protocol mentioned (amqp) is not supported by Kafka and hence one of the following changes are suggested
The example should be changed to have kafka in protocol, OR
The following text should mention some other message queue which supports AMQP (something like RabbitMQ)
Since the description (and the host) mention broker, I believe the intentions of the publisher was originally to mention amqp and hence the text should be changed.
Let me know of your thoughts. 🙂
Attach any resources that can help us understand the issue.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
Describe the bug you found in AsyncAPI Docs.
In the Adding Security page, the protocol mentioned in the example is
amqp
however the following text readsThe protocol mentioned (
amqp
) is not supported by Kafka and hence one of the following changes are suggestedkafka
in protocol, ORSince the description (and the host) mention broker, I believe the intentions of the publisher was originally to mention
amqp
and hence the text should be changed.Let me know of your thoughts. 🙂
Attach any resources that can help us understand the issue.
Code of Conduct
The text was updated successfully, but these errors were encountered: