Bug 535538 (RHQ-2222) - Installer: db "Test Connection" button clears password field
Summary: Installer: db "Test Connection" button clears password field
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: RHQ-2222
Product: RHQ Project
Classification: Other
Component: Installer
Version: 4.2
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: Jay Shaughnessy
QA Contact: Jeff Weiss
URL: http://jira.rhq-project.org/browse/RH...
Whiteboard:
: 772226 881400 (view as bug list)
Depends On:
Blocks: jon30-sprint9 jon30-sprint10, rhq43-sprint10
TreeView+ depends on / blocked
 
Reported: 2009-07-08 19:15 UTC by Jeff Weiss
Modified: 2014-11-09 22:49 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
rev4268
Last Closed: 2013-09-04 07:30:36 UTC
Embargoed:


Attachments (Terms of Use)

Description Jeff Weiss 2009-07-08 19:15:00 UTC
To repeat:

bring up installer page, fill out db connection info (including password).  Click "Test Connection".  The connection test passes (green icon), but the password field has been cleared and the user is forced to re-enter their password.  This is a regression in the latest qa build, in all previous builds the field would remain intact.



Comment 1 Charles Crouch 2009-07-28 23:47:00 UTC
If this is easy and quick to do then lets do it, otherwise push.

Comment 2 Joseph Marques 2009-09-03 12:17:24 UTC
this button actually performs a full-page form submit, an action, then redirects back to itself.  to fix this, we'd have to move to an ajax-y button whose action handler updated some element on the page.  pretty simple, but i vote to push given the time left in this release.  

Comment 3 Charles Crouch 2009-09-03 15:56:50 UTC
+1 on pushing. This is annoying but not a showstopper.

Comment 4 Jeff Weiss 2009-09-03 16:20:40 UTC
This is a regression, it used to work fine.  How is ajax required now, but not before?

Comment 5 Red Hat Bugzilla 2009-11-10 21:00:16 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2222


Comment 6 Charles Crouch 2010-05-17 21:41:21 UTC
IIRC currently the user is not required to re-enter their password after testing the DB connection

Comment 7 Ian Springer 2011-11-21 16:41:24 UTC
This is still an issue in JON 3.0.CR2. 

The password field gets blanked out after the Test Connection button is clicked, and then the installer allows the user to click the Install button even though the password is blank (password should be a required field so validation fails if it is blank..), and then the install fails and causes the rhq oracle user to be locked due to too many failed attempts trying to login with a blank password.

Comment 9 Jay Shaughnessy 2011-12-16 16:25:14 UTC
Maintaining the password value is actually not easy given the installer
impl.  This should probably be fixed as a result of building a new
installer implemented in SmartGWT, as part of our move away from JSF.

In the interim, I'll see if I can just ensure that we have a value
filled in prior to exiting the page.

Comment 10 Jay Shaughnessy 2011-12-16 22:10:08 UTC
commit 14256b6e778bbb02703dd82e1804f69d2b639f64

An attempt to improve the situation by alerting the user, and not processing
"Test Connection" or "Install Server!" buttons,  if the password field
is empty.
- Note, the message displayed is in English since I'm not proficient enough
  to figure out how to get javascript to interact with the resource bundle.


Test Notes
Would need to test this on the supported browsers I guess.

Comment 11 Sunil Kondkar 2011-12-19 12:13:30 UTC
Verified in master build#848

Verified on browsers Firefox 3.x , IE 8 and chrome. If password field is empty and user clicks on the "Test Connection" button on the installer page, it displays a message "Please enter database password".

Comment 12 Charles Crouch 2012-01-12 03:11:49 UTC
*** Bug 772226 has been marked as a duplicate of this bug. ***

Comment 13 Charles Crouch 2012-01-12 03:16:40 UTC
Setting this back to ONQA to make sure that "Install Server!" button doesn't trigger an install attempt if the database password field is empty. This should prevent the issue which Ian mentioned.

Comment 14 Mike Foley 2012-01-16 15:23:42 UTC
additionally verified the testpoint in comment #13

Comment 15 mark yarborough 2012-11-29 20:13:45 UTC
*** Bug 881400 has been marked as a duplicate of this bug. ***

Comment 16 Heiko W. Rupp 2013-09-04 07:30:36 UTC
Done in a very old release, closing now.


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