Bug 694857

Summary:	[RFE] condor_trigger_config should allow to specify the authentication method for qpidd
Product:	Red Hat Enterprise MRG	Reporter:	Luigi Toscano <ltoscano>
Component:	condor-qmf	Assignee:	Robert Rati <rrati>
Status:	CLOSED ERRATA	QA Contact:	Jan Sarenik <jsarenik>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	Development	CC:	iboverma, jsarenik, matt
Target Milestone:	2.0
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	condor-7.6.1-0.3	Doc Type:	Bug Fix
Doc Text:	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	Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-23 15:39:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	693778

Description Luigi Toscano 2011-04-08 16:06:16 UTC

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).

Comment 1 Robert Rati 2011-04-21 20:54:54 UTC

Added -U, -P, -m arguments to condor_trigger_config for specifying authentication params.

Fixed upstream on V7_6-branch

Comment 3 Robert Rati 2011-05-05 13:49:51 UTC

    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

Comment 4 Jan Sarenik 2011-05-25 11:16:48 UTC

Authentication methods verified with condor-qmf-7.6.1-0.4.el5

Tested on PLAIN and ANYNOMOUS, both positive and negative
scenarios.

Comment 5 errata-xmlrpc 2011-06-23 15:39:57 UTC

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