Bug 691797 - RFE: Allow specifying more than 1 authentication method
Summary: RFE: Allow specifying more than 1 authentication method
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-qmf
Version: Development
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-29 13:54 UTC by Robert Rati
Modified: 2021-03-16 12:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Robert Rati 2011-03-29 13:54:03 UTC
Description of problem:
The ruby and python qmf apis allow to specify more than 1 authentication method, however the C++ api only allows specifying 1 authentication method.  It would be nice if all the apis aligned to allow multiple authentication methods.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Gordon Sim 2011-03-31 09:11:26 UTC
http://svn.apache.org/viewvc?view=revision&revision=1078733 (part of fix to https://bugzilla.redhat.com/show_bug.cgi?id=661500) adds this ability to the underlying c++ messaging client. Whether that is sufficient for QMF also needs to still be verified.

Comment 2 Justin Ross 2013-02-26 21:22:35 UTC
Ted, where does this stand?

(In reply to comment #1)
> http://svn.apache.org/viewvc?view=revision&revision=1078733 (part of fix to
> https://bugzilla.redhat.com/show_bug.cgi?id=661500) adds this ability to the
> underlying c++ messaging client. Whether that is sufficient for QMF also
> needs to still be verified.

Comment 3 Ted Ross 2013-05-13 15:06:07 UTC
As we move to the newer QMFv2 interfaces, this issue will be resolved.  The QMFv2 APIs don't deal with connections directly, they use connections that were established through the normal messaging API.  This allows QMF to use any connection feature supported by messaging.


Note You need to log in before you can comment on or make changes to this bug.