Description of problem: As in title. Version-Release number of selected component (if applicable): spqr-0.3.3 How reproducible: Specify a username but select another authentication mechanism (e.g. "ANONYMOUS"). Actual results: SPQR will use PLAIN. Expected results: SPQR should use the specified authentication mechanism and only fall back to PLAIN when a user id is specified but no mechanism is. Additional info:
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: C: The SPQR library, which is used by the Wallaby service, is designed to automatically select an authentication mechanism based on certain selected options if one is not explicitly specified. However, if a user specified a username and the ANONYMOUS mechanism, SPQR would override the user's explicit mechanism selection and instead choose PLAIN authentication. C: This behavior is confusing to users. F: SPQR now prioritizes explicitly-specified mechanisms over implicitly-selected ones. R: SPQR and services built upon it should now behave as users expect them to.
Successfully reproduced with: ruby-spqr-0.3.3-1 # cat /usr/lib/ruby/site_ruby/1.8/spqr/app.rb ... settings.mechanism = @explicit_mechanism || implicit_mechanism ... using setting "export WALLABY_BROKER_MECHANISM=GSSAPI" in /etc/sysconfig/wallaby-agent without user or password spqr always use "ANONYMOUS", if those two are filled it always uses "PLAIN"
Tested with: ruby-spqr-0.3.5-1 Tested on: RHEL5 i386,x86_64 RHEL6 i386,x86_64 # cat /usr/lib/ruby/site_ruby/1.8/spqr/app.rb ... settings.mechanism = @qmf_explicit_mechanism || implicit_mechanism ... spqr uses chosen mechanism >>> VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-0100.html