Description of problem: condor_trigger_config does not currently allow to specify the authentication method to connect to qpidd. Depending on the settings, condor_trigger_config could be useless. Version-Release number of selected component (if applicable): condor-qmf-7.6.0-0.4 (all supported architectures).
Added -U, -P, -m arguments to condor_trigger_config for specifying authentication params. Fixed upstream on V7_6-branch
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: Attempting to configure the triggerd through a secured broker C: Configuring a triggerd through a secured broker was not possible C: Added new option to condor_trigger_config to allow communication through a secured broker R: It is now possible to configure the triggerd through a secured broker
Authentication methods verified with condor-qmf-7.6.1-0.4.el5 Tested on PLAIN and ANYNOMOUS, both positive and negative scenarios.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2011-0889.html