activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bhartsb <bhar...@cox.net>
Subject Re: Problem with STOMP C++ Client connecting with a AMQ Broker having Authorization and Authentication Plugins installed
Date Fri, 10 Nov 2006 20:32:05 GMT


Yes either Avinash or Aditya has previously opened a JIRA issue.  I don't
know if anyone has claimed it however, nor an ETA.

Thanks.


nmittler wrote:
> 
> As far as I can tell, the activemq-cpp client should handle this properly
> (
> i.e. throw an exception on receipt of a stomp error frame).
> 
> It sounds like this problem has been brought up before - has a JIRA issue
> been created?  If not, please create one, and I'll take a crack at it.
> 
> Thanks,
> Nate
> 
> On 11/10/06, bhartsb <bhartsb@cox.net> wrote:
>>
>>
>> Hi I'll chime in here as this work discussed is being done for me.
>>
>> First, you are correct that the CONNECTED msg is coming from the
>> broker...I
>> think that was just a typing error by my developer.
>>
>> As for the issue, the C++ call createConnection() creates a low level
>> connection(assume), and passes credentials. Then the broker should send a
>> STOMP ERROR msg back (if credentials are wrong) and disconnect.  It seems
>> this has already been discussed with regard to the RUBY client:
>>
>>
>> http://www.nabble.com/Proper-behavior-for-client-authorization-failure-tf2497200.html
>>
>> If the C++ app. upon receiving ERROR then wants to create an exception, I
>> suppose it could.
>>
>> Any ETA for this fix?
>>
>> Thanks.
>>
>> Hiram Chirino wrote:
>> >
>> > I'm thinking an ERROR should be sent back if an invalid CONNECT is
>> > given and then the connection should just get terminated.
>> >
>> > On 11/8/06, Timothy Bish <tabish@twcny.rr.com> wrote:
>> >>
>> >> >
>> >> > Thanks for your reply.
>> >> >
>> >> > We are not getting any errors when we are trying to send/receive
>> >> message.
>> >> >
>> >> > What we require here is that, when we are sending wrong credentials
>> to
>> >> the
>> >> > AMQ Broker, the C++ ActiveMQ client should be able to get the
>> >> > Authentication
>> >> > failed error code.
>> >>
>> >> Right we get that, we just wanted to know how much functionality the
>> >> stomp
>> >> client had when connected with bad credentials.  Sounds like none is
>> what
>> >> you're seeing.
>> >>
>> >> >
>> >> > The 'CONNECTED' message is not being sent by AMQ Broker at all, as
>> the
>> >> > plug-in is installed in the Broker.
>> >> >
>> >> > This 'CONNECTED' message we are receiving in the
>> SocketInputStream.cpp
>> >> > class
>> >> > present under C++ ActiveMQ client.
>> >>
>> >> The connected message would have to be coming from the Broker as the
>> CPP
>> >> client wouldn't spuriously create one for you.  We are looking into
>> what
>> >> the
>> >> correct behavior should be given the limitations of the stomp
>> protocol.
>> >>
>> >> We'll keep you posted on the fix.
>> >>
>> >> Regards
>> >> Tim
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>> > --
>> > Regards,
>> > Hiram
>> >
>> > Blog: http://hiramchirino.com
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Problem-with-STOMP-C%2B%2B-Client-connecting-with-a-AMQ-Broker-having-Authorization-and-Authentication-Plugins-installed-tf2582789.html#a7274843
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
> 
> 

-- 
View this message in context: http://www.nabble.com/Problem-with-STOMP-C%2B%2B-Client-connecting-with-a-AMQ-Broker-having-Authorization-and-Authentication-Plugins-installed-tf2582789.html#a7284666
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message