amqp:ssl:myhost.mydomain:5671 options << transport => 'ssl' But, no dice :-/
Thanks for the help though! Trevor On Wed, Oct 23, 2013 at 10:01 AM, Gordon Sim <[email protected]> wrote: > On 10/23/2013 01:36 PM, Trevor Vaughan wrote: > >> Thanks for getting back to me. >> >> The C++ broker is working fine, I can use the Python code to connect to >> the >> broker over SSL with no issues whatsoever. >> >> Unfortunately, the Ruby client code isn't behaving so well. >> >> The client DB only has the list of trusted CA's with the TC flags set >> since >> I'm not trying to use client certificates. >> >> I did use the FQDN, DNS works properly, and I am going to port 5671. >> > > Sorry for all the stupid questions then ;-) Just one more... > > What url are you giving to the ruby client to tell it to use ssl? It > doesn't recognise the 'amqps' scheme the python client uses. However you > can use ssl:myhost.mydomain:5671 to indicate that ssl should be used, or > indeed set a connection level option for 'transport' to 'ssl' (not exactly > sure how you do that in ruby). > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > [email protected].**org<[email protected]> > For additional commands, e-mail: [email protected] > > -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 [email protected] -- This account not approved for unencrypted proprietary information --
