[rabbitmq-discuss] two factor authentication with tokens
simon at rabbitmq.com
Fri Jan 11 15:01:59 GMT 2013
Yes, that's how it's intended to work.
On 11/01/13 14:59, Ben Hood wrote:
> Hi all,
> In order to implement this, would this be a case of:
> * Configure a client side SASLMechanism that supplies a token;
> * Configure the server to accept this mechanism;
> * Implement a rabbit_auth_mechanism behavior that defers the
> processing of the token to some upstream provider;
> On Thursday, 10 January 2013 at 00:36, Jerry Kuch wrote:
>> Hi, Thomas:
>> Not out of the box... although the Rabbit authentication and
>> authorization mechanisms are pluggable and can be replaced if one is
>> willing to write a bit of Erlang.
>> To that end, how does one implement the server end of RSA-token based
>> two factor authentication? Is there an SDK or APIs that one must gain
>> access to?
>> Also, two factor auth seems most useful when there's a human involved
>> in the log-on process, something which for a messaging broker may
>> often not really be true. Can you say more about the nature of your
>> desire for RSA two factor with Rabbit?
>> Best regards,
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> <mailto:rabbitmq-discuss at lists.rabbitmq.com>
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss