<div>Hi all,</div><div><br></div><div>In order to implement this, would this be a case of:</div><div><br></div><div><ul><li>Configure a client side SASLMechanism that supplies a token;</li><li>Configure the server to accept this mechanism;</li><li>Implement a rabbit_auth_mechanism behavior that defers the processing of the token to some upstream provider;</li></ul>?</div><div><br></div><div>Cheers,</div><div><br></div><div>Ben </div>
<p style="color: #A0A0A8;">On Thursday, 10 January 2013 at 00:36, Jerry Kuch wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>Hi, Thomas:<div><br></div><div>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.</div><div><br></div><div>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?</div>
<div><br></div><div>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?</div>
<div><br></div><div>Best regards,</div><div>Jerry</div><div><br></div>
</div><div><div>_______________________________________________</div><div>rabbitmq-discuss mailing list</div><div><a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a></div><div><a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>