-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
LDAP plugin does not interpolate values with non-ASCII characters such as ß #9059
Comments
@MichaelUray are there any exceptions, errors, or warnings in the RabbitMQ log? What RabbitMQ version is used and running on what Erlang version? |
RabbitMQ 3.11.13 It looks to me the server crashes: Log
|
@MichaelUray we have a PR ready: #9149. You can try it out using Can you give it a try and see if strings with a ß are correctly handled (interpolated) by the LDAP plugin? |
I can confirm that it works with pivotalrabbitmq/rabbitmq:fix-9059-otp-max-bazel. Thanks for addressing that so quickly. |
@MichaelUray you can see that the PR has a milestone set on it, It should not take long, intend to ship another round of patches very soon because of another issue addressed for a paying customer. Thank you for confirming the fix, by the way! |
Describe the bug
If there is a "ß" character (probably same issue on other non ASCII-128 characters) used in the topic, then the topic_access_query permission does not work on MQTT topics which get their permissions from an LDAP attribute.
Reproduction steps
RabbitMQ 3.11.13
Erlang 25.3
Create a topic as followed:
Plants/City1/Hauptstraße/150
Set the LDAP
postal
attribute of the user who connects toPlants.City1.Hauptstraße.150
Set the permission in the
advanced.config
file as followed:It is not possible to write to this topic.
If I replace the "ß" with "ss" in the topic as well as in the
postal
attribute, then it applies the permissions.Expected behavior
I would expect that the permission gets applied independent from the used characters in the MQTT topic.
Additional context
The text was updated successfully, but these errors were encountered: