Closed sossnowski closed 1 year ago
Thanks @sossnowski for reporting this issue. The issue is present when using Oauth2 with AMQP 1.0 plugin in RabbitMQ 3.11.x. It does not occur in 3.12-rc. I have bumped the version of RabbitMQ to 3.12-rc-management. In the meantime, I am investigating this issue. I will report you back thru this same ticket.
@sossnowski This issue is now fixed in 3.11.12 release. Closing this ticket for now.
Hi, unfortunately I still can not connect to rabbitmq using steps from your readme file with use AMQP1.0 (NODE.js RHEA and KEYCLOAK) with OAUTH2.0 token. I am using token generated by Pika producer from your repo pika-client/producer.py (pika is able to connect and everything is ok with it- pika is using AMQP 0.9 protocol), but when I try the same token to connect with AMQP1.0 (with Node.js RHEA) I get:
I am not able to resolve this error, I dont understand why user is authenticated firstly, but later I have message tat token is invalid (while when pika with AMQP0.9 uses it - is valid).
Any suggestions?