Our team does not use GitHub issues for questions and discussions.
RabbitMQ 3.8 will be released in the next few months. We are fairly confident that the beta versions are quite stable and early adopters should not run into any major issues. If you really need one of the new features in 3.8, I'd consider starting with beta releases.
This plugin depends on internal
authnandauthzchanges in RabbitMQ server. They were necessary so that authorization operations have access to the password (in 3.7 they don't, as other backends do not need it). This in turn lets you specify the token in the password field. Early versions of this plugin used the username for that but that value is logged in many cases, and since tokens are sensitive values, this was only acceptable for a prototype.
Modifying the plugin will not make it 3.7 compatible. You have to modify RabbitMQ itself.I'd recommend either not using the plugin or adopting a 3.8 beta. A first 3.8 RC is expected next month.
> To unsubscribe from this group and stop receiving emails from it, send an email to rabbitm...@googlegroups.com.