Having only write rights to queue with Bunny gem
I use the Bunny gem and configured a user in RabbitMQ like this:
virtual host /
configure: device1..*
write: .*
read: device1..*
The goal is: the user should be able to create a queue named like this: device1.mail and should be able to read / write to it.
To all other queues I only want to give the user write access (but not read).
When I try to write to an existing durable queue named calc with Bunny I get an error:
conn = Bunny.new('amqp://device1:device1@128.0.0.0:5672')
conn.start
ch = conn.create_channel
q = ch.queue("calc", durable: true)
Bunny::AccessRefused (ACCESS_REFUSED - access to queue 'calc' in vhost '/' refused for user 'device1')
When I set the configure rights to .* for the user, then it works. I'm able to write to the queue, but not read. However like that the user can create queues named like he wants...
So it seems the configure right is needed in order to open the queue (even though it's an existing queue?).
What am I missing here?
bunny
add a comment |
I use the Bunny gem and configured a user in RabbitMQ like this:
virtual host /
configure: device1..*
write: .*
read: device1..*
The goal is: the user should be able to create a queue named like this: device1.mail and should be able to read / write to it.
To all other queues I only want to give the user write access (but not read).
When I try to write to an existing durable queue named calc with Bunny I get an error:
conn = Bunny.new('amqp://device1:device1@128.0.0.0:5672')
conn.start
ch = conn.create_channel
q = ch.queue("calc", durable: true)
Bunny::AccessRefused (ACCESS_REFUSED - access to queue 'calc' in vhost '/' refused for user 'device1')
When I set the configure rights to .* for the user, then it works. I'm able to write to the queue, but not read. However like that the user can create queues named like he wants...
So it seems the configure right is needed in order to open the queue (even though it's an existing queue?).
What am I missing here?
bunny
add a comment |
I use the Bunny gem and configured a user in RabbitMQ like this:
virtual host /
configure: device1..*
write: .*
read: device1..*
The goal is: the user should be able to create a queue named like this: device1.mail and should be able to read / write to it.
To all other queues I only want to give the user write access (but not read).
When I try to write to an existing durable queue named calc with Bunny I get an error:
conn = Bunny.new('amqp://device1:device1@128.0.0.0:5672')
conn.start
ch = conn.create_channel
q = ch.queue("calc", durable: true)
Bunny::AccessRefused (ACCESS_REFUSED - access to queue 'calc' in vhost '/' refused for user 'device1')
When I set the configure rights to .* for the user, then it works. I'm able to write to the queue, but not read. However like that the user can create queues named like he wants...
So it seems the configure right is needed in order to open the queue (even though it's an existing queue?).
What am I missing here?
bunny
I use the Bunny gem and configured a user in RabbitMQ like this:
virtual host /
configure: device1..*
write: .*
read: device1..*
The goal is: the user should be able to create a queue named like this: device1.mail and should be able to read / write to it.
To all other queues I only want to give the user write access (but not read).
When I try to write to an existing durable queue named calc with Bunny I get an error:
conn = Bunny.new('amqp://device1:device1@128.0.0.0:5672')
conn.start
ch = conn.create_channel
q = ch.queue("calc", durable: true)
Bunny::AccessRefused (ACCESS_REFUSED - access to queue 'calc' in vhost '/' refused for user 'device1')
When I set the configure rights to .* for the user, then it works. I'm able to write to the queue, but not read. However like that the user can create queues named like he wants...
So it seems the configure right is needed in order to open the queue (even though it's an existing queue?).
What am I missing here?
bunny
bunny
asked Nov 9 at 22:22
rept
81211130
81211130
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You need to set passive to true when declaring the queue. With passive set to true the configure permission will not applied and an error will be raised if the user try to create a non pre-defined queue.
q = ch.queue("calc", durable: true, passive: true)
Thanks, this indeed does the trick!
– rept
Nov 11 at 23:22
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53234031%2fhaving-only-write-rights-to-queue-with-bunny-gem%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You need to set passive to true when declaring the queue. With passive set to true the configure permission will not applied and an error will be raised if the user try to create a non pre-defined queue.
q = ch.queue("calc", durable: true, passive: true)
Thanks, this indeed does the trick!
– rept
Nov 11 at 23:22
add a comment |
You need to set passive to true when declaring the queue. With passive set to true the configure permission will not applied and an error will be raised if the user try to create a non pre-defined queue.
q = ch.queue("calc", durable: true, passive: true)
Thanks, this indeed does the trick!
– rept
Nov 11 at 23:22
add a comment |
You need to set passive to true when declaring the queue. With passive set to true the configure permission will not applied and an error will be raised if the user try to create a non pre-defined queue.
q = ch.queue("calc", durable: true, passive: true)
You need to set passive to true when declaring the queue. With passive set to true the configure permission will not applied and an error will be raised if the user try to create a non pre-defined queue.
q = ch.queue("calc", durable: true, passive: true)
answered Nov 11 at 5:14
Abdulrazak Alkl
635511
635511
Thanks, this indeed does the trick!
– rept
Nov 11 at 23:22
add a comment |
Thanks, this indeed does the trick!
– rept
Nov 11 at 23:22
Thanks, this indeed does the trick!
– rept
Nov 11 at 23:22
Thanks, this indeed does the trick!
– rept
Nov 11 at 23:22
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53234031%2fhaving-only-write-rights-to-queue-with-bunny-gem%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown