Created attachment 1078752 [details] Screenshot showing result of password containing spaces. Description of problem: When configuring the CFME appliance with an internal database with a password, passwords which contain non-alphanum characters ([^a-zA-Z0-9]) may cause DB configuration to fail. Version-Release number of selected component (if applicable): Verified on CFME 5.3.4 for VMware, but may affect other releases. How reproducible: 100% Steps to Reproduce: 1. Deploy appliance 2. In the console, select option 8 to configure the DB. 3. Configure an internal DB with the following password content (without the quotes) "a passphrase with spaces" Actual results: DB fails to configure, reporting the following postgres error: role "root" does not exist. Expected results: Option 1: The DB is configured successfully. Option 2: Alternatively, if "special" characters are not allowed in the password, an input validation error should be reported before attempting to configure the DB. Additional info: Screenshot attached which shows the error.
https://github.com/ManageIQ/manageiq/pull/4625
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/f06ff61a002383912c17e01091f026b9f7576de7 commit f06ff61a002383912c17e01091f026b9f7576de7 Author: Nick Carboni <ncarboni> AuthorDate: Thu Oct 1 14:31:27 2015 -0400 Commit: Nick Carboni <ncarboni> CommitDate: Thu Oct 1 14:31:27 2015 -0400 Use PG utility to create the postgres role This allows us to avoid nasty quoting and escaping issues associated with shelling out to run commands using psql. This also allow us to use PG's built in string escape method so passwords can now contain all manner of special characters. https://bugzilla.redhat.com/show_bug.cgi?id=1267698 gems/pending/appliance_console/internal_database_configuration.rb | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
Verified in 5.5.0.11 with password " !!££%%&&(("
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. https://access.redhat.com/errata/RHSA-2015:2551