Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Topic access check broken because of variable map in the context #16

Closed
acogoluegnes opened this issue Jun 26, 2017 · 0 comments
Closed

Topic access check broken because of variable map in the context #16

acogoluegnes opened this issue Jun 26, 2017 · 0 comments
Assignees
@acogoluegnes
Labels
bug effort-low
Milestone
3.7.0

Comments

@acogoluegnes
Copy link
Contributor

rabbitmq/rabbitmq-server#1229 introduced a variableMap in the context argument of rabbit_authz_backend:check_topic_access/4 and the AMQP backend doesn't handle the conversion of a map into AMQP headers.
@acogoluegnes acogoluegnes added this to the 3.7.0 milestone Jun 26, 2017
@acogoluegnes acogoluegnes self-assigned this Jun 26, 2017
acogoluegnes added a commit that referenced this issue Jun 30, 2017
@acogoluegnes
Handle map when building AMQP message headers
071e28d 
An Erlang map is turned in to several headers. E.g.
{variable_map, #{username => guest, vhost = some-vhost}} is converted
into 2 headers: variable_map.username=guest and variable_map.vhost=some-vhost.

Fixes #16
@acogoluegnes acogoluegnes mentioned this issue Jun 30, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@acogoluegnes acogoluegnes

Labels
bug effort-low
Projects
None yet
Milestone
3.7.0
Development

No branches or pull requests
1 participant
@acogoluegnes