Bug 620912 – ruby console attempts to use bad credentials repeatedly

Bug 620912 - ruby console attempts to use bad credentials repeatedly

Summary:	ruby console attempts to use bad credentials repeatedly

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	qpid-qmf (Show other bugs)
Sub Component:
Version:	Development
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	messaging-bugs
QA Contact:	MRG Quality Engineering
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:
Blocks:	612425
	Show dependency tree / graph

Reported:	2010-08-03 14:37 EDT by Will Benton
Modified:	2014-06-17 14:28 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:	612425
Environment:
Last Closed:	2014-06-17 14:28:04 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Will Benton 2010-08-03 14:37:20 EDT

+++ This bug was initially created as a clone of Bug #612425 +++

Description of problem:
The ruby QMF console will repeatedly attempt to use bad credentials instead of failing.  (Observed in wallaby-utils.)

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

ruby-qmf 0.7.946106-10

How reproducible:
100%

Steps to Reproduce:
1. Run a QMF console application, e.g. wallaby-inventory, with bad supplied credentials
  
Actual results:
The tool attempts to use the bad credentials indefinitely
The tool repeat the same message over and over again
'warning Broker closed connection: 320, connection-forced: Authentication failed'

Expected results:
The QMF engine should raise an exception after some configurable number of failed authentication attempts.

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