Personally I feel using PKI is a much better solution than any proprietary windows protocol. I would also guess that the majority of users using rabbit are using it in unix environments at this point.<div><br></div><div>The certificate based authentication works like a charm, just need to update it to support the full�gamut�of PKI functionality. From a security standpoint, it's much better to encrypt the communication channel.<div>
<div><br></div><div>Mark Steele<br>Director of development<br>Bering Media Inc.<br><br>
<br><br><div class="gmail_quote">On Fri, Jul 16, 2010 at 10:05 AM, Dan Wise <span dir="ltr"><<a href="mailto:Dan.Wise@ignisasset.com">Dan.Wise@ignisasset.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-GB" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;color:blue">Yes, this confirms the issue I was worrying about. </span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:blue">�</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:blue">I think it would be very valuable to add NTLM authentication to
Rabbit on Windows, so that only a username could be supplied on the client and
the authentication verified on the server, without the need to pass clear-text
passwords or per-user SSL certificates. This would really enhance the
commercial attractiveness of Rabbit.</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:blue">�</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:blue">Anyone want to take up the challenge?</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:blue">�</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:blue">Dan.</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:blue">�</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:blue">�</span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt">From:</span></b><span lang="EN-US" style="font-size:10.0pt"> Mark Steele
[mailto:<a href="mailto:msteele@beringmedia.com" target="_blank">msteele@beringmedia.com</a>] <br>
<b>Sent:</b> 16 July 2010 13:44</span></p><div><div></div><div class="h5"><br>
<b>To:</b> Dan Wise<br>
<b>Cc:</b> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<b>Subject:</b> Re: [rabbitmq-discuss] Authenticating users via SSPI</div></div><p></p>
</div><div><div></div><div class="h5">
<p class="MsoNormal">�</p>
<p class="MsoNormal">Really depends on what your needs are.</p>
<div>
<p class="MsoNormal">�</p>
</div>
<div>
<p class="MsoNormal">You could have one cert per user, and use the same
authentication information in your rabbit cloud for all users. I just noticed
however that the erlang new_ssl implementation does not support CRLs, so you
won't be able to revoke a certificate and have that reflected by an
authentication failure on the rabbit server.</p>
</div>
<div>
<p class="MsoNormal">�</p>
</div>
<div>
<p class="MsoNormal">Wonder what the odds of adding CRL or OCSP support to rabbit
are....There was a thread about this in 2009:�<a href="http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2009-July/004189.html" target="_blank">http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2009-July/004189.html</a></p>
</div>
<div>
<p class="MsoNormal">�</p>
</div>
<div>
<p class="MsoNormal">Both these functionalities are pretty trivial to implement
using the openssl library</p>
</div>
<div>
<p class="MsoNormal">�</p>
</div>
<div>
<p class="MsoNormal">So I guess my original suggestion doesn't fly as a good
solution, sorry!</p>
</div>
<div>
<p class="MsoNormal">�</p>
</div>
<div>
<p class="MsoNormal">Cheers,</p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br clear="all">
Mark Steele<br>
Director of development<br>
Bering Media Inc.<br>
<br>
<br>
</p>
<div>
<p class="MsoNormal">On Thu, Jul 15, 2010 at 6:33 PM, Dan Wise <<a href="mailto:Dan.Wise@ignisasset.com" target="_blank">Dan.Wise@ignisasset.com</a>> wrote:</p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;color:blue">Would I need a separate certificate for each
user? Does peer certificate verification bypass normal username and password
checking?</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:blue">�</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:blue">Dan.</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:blue">�</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:blue">�</span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt">From:</span></b><span lang="EN-US" style="font-size:10.0pt"> Mark Steele [mailto:<a href="mailto:msteele@beringmedia.com" target="_blank">msteele@beringmedia.com</a>]
<br>
<b>Sent:</b> 15 July 2010 14:52<br>
<b>To:</b> Dan Wise<br>
<b>Cc:</b> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<b>Subject:</b> Re: [rabbitmq-discuss] Authenticating users via SSPI</span></p>
</div>
<p class="MsoNormal">�</p>
<p class="MsoNormal">You
could use PKI and store the certificates in LDAP. Have your app use the current
credentials of the user to grab the certificate and connect to rabbit over SSL
with peer certificate verification enabled.</p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br clear="all">
Mark Steele<br>
Director of development<br>
Bering Media Inc.<br>
<br>
</p>
</div>
<div>
<p class="MsoNormal">On
Thu, Jul 15, 2010 at 5:53 AM, Dan Wise <<a href="mailto:Dan.Wise@ignisasset.com" target="_blank">Dan.Wise@ignisasset.com</a>>
wrote:</p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;color:navy">Hi,</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:navy">�</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:navy">We have a number of Windows users who want
to use our rabbitmq messaging. However we need to ensure that we authenticate them
without them having to enter their Windows passwords and syncing with the
rabbitmq user passwords.</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:navy">�</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:navy">Has anyone looked at a mechanism for using
SSPI authentication to allow clients to connect? This is surely a common
challenge, particularly in an organisation where there are large numbers of
users and the job of providing and maintaining separate passwords for different
systems is hugs.</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:navy">�</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:navy">Thanks,</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;color:navy">�</span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:10.0pt;color:#1F497D">Dan Wise</span></b></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:10.0pt;color:#1F497D">�</span></b></p>
<p class="MsoNormal">�</p>
</div>
<p class="MsoNormal">**************************************************************<br>
<br>
Visit our Website at <a href="http://www.ignisasset.com/" target="_blank">http://www.ignisasset.com/</a>
<br>
The information contained in this email (including any attachments transmitted
within it) is confidential and is intended solely for the use of the named
person. <br>
The unauthorised access, copying or re-use of the information in it by any
other person is strictly forbidden. <br>
If you are not the intended recipient please notify us immediately by return
email to <a href="mailto:postmaster@ignisasset.com" target="_blank">postmaster@ignisasset.com</a>.<br>
<br>
Internet communication is not guaranteed to be timely, secure, error or virus
free. We accept no liability for any harm to systems or data, nor for personal
emails. Emails may be recalled, deleted and monitored.<br>
<br>
Ignis Asset Management is the trading name of the Ignis Asset Management
Limited group of companies which includes the following subsidiary and
associated companies: Ignis Asset Management Limited (Registered in Scotland
No. SC200801), Ignis Investment Services Limited* (Registered in Scotland No.
SC101825) <br>
Ignis Fund Managers Limited* (Registered in Scotland No. SC85610) Scottish
Mutual Investment Managers Limited* (Registered in Scotland No. SC88674) <br>
Registered Office: 50 Bothwell Street, Glasgow, G2 6HR, Tel: 0141-222-8000 and
Scottish Mutual PEP & ISA Managers Limited* (Registered in England No.
971504)<br>
Registered Office: 1 Wythall Green Way, Wythall, Birmingham B47 6WG and Ignis
Investment Management Limited* (Registered in England No. 5809046) <br>
Registered Office: Sentinel House, 16 Harcourt Street, London, W1H 4AD.
Scottish Mutual is a registered trade mark of Scottish Mutual Assurance Limited<br>
<br>
*Authorised and regulated by the Financial Services Authority.<br>
<br>
**************************************************************</p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a></p>
</div>
</div>
<p class="MsoNormal">�</p>
</div>
</div>
</div>
</div>
<p class="MsoNormal">�</p>
</div>
</div></div></div>
</div>
</blockquote></div><br></div></div></div>