[rabbitmq-discuss] API for Acess Control

[Alexis Richardson]

Desrie

You could build a GUI in .NET using any .NET tools you like, and make
use of the Alice HTTP management interface that I sent you a link to.
 That way not only do you not have to read Erlang, but you can use
HTTP to talk to RabbitMQ instead of AMQP :-)

For example see this use case from
http://willcodeforfoo.com/2009/07/13/announcing-alice/.  Below the
example is using curl but you could make the HTTP call from your .NET
client...

# Setting permissions
curl -i -XPOST -d '{"vhost":"/", "configure":".*", "read":".*", "write":".*"}' \
  http://localhost:9999/permissions/guest
HTTP/1.1 200 OK
Server: MochiWeb/1.0 (Any of you quaids got a smint?)
Date: Tue, 04 Aug 2009 07:55:33 GMT
Content-Type: text/json
Content-Length: 38

{"permissions":[["/",".*",".*",".*"]]}

Does that get you what you need?

alexis


On Fri, Nov 6, 2009 at 10:31 AM, Desrie Qi <desrie.qi at wealthcraft.com> wrote:
> Matthias
>
> I just want to build a web UI myself by .Net AMQP API to achieve manage RabbitMQ permissions. I have difficulty to read Erlang.
>
> Thanks
> Desrie
>
> -----Original Message-----
> From: Matthias Radestock [mailto:matthias at lshift.net]
> Sent: Friday, 6 November 2009 4:12 PM
> To: Desrie Qi
> Cc: Alexis Richardson; rabbitmq-discuss at lists.rabbitmq.com
> Subject: Re: [rabbitmq-discuss] API for Acess Control
>
> Desrie,
>
> Desrie Qi wrote:
>> Do you mean currently is not possible for client to control this by win/web UI for RPC?
>
> You asked about .NET APIs. If you want a win/web UI, then there are
> existing monitoring and "management" UIs that people have written. IIRC
> some of them allow configuration of the broker, rather than just
> monitoring, but I could be wrong. Alexis may have a list somewhere of
> the UIs we are currently aware of.
>
>
> Regards,
>
> Matthias.
>