Created attachment 972508 [details] screenshot that shows that a trusted forest entry with blank fields can be added Description of problem: ------------------------- I ran into this issue while verifying bug 1163384. See attached screenshot. Version-Release number of selected component (if applicable): --------------------------- 5.3.2.5 How reproducible: ---------------- Always Steps to Reproduce: ---------------- 1. Go to Configuration/Configure 2. Select Current server in Settings Accordion 3. Go to Authentication tab 4. change mode to LDAP 5. Check the checkbox for "Get User Groups from LDAP" 6. In "Trusted Forest Settings" box, click on + sign to Add a new forest 7. While entering new Forest details,leave all the fields blank and then press "Add this entry" button. Actual results: --------------- CFME allows a user to add a Trusted forest entry even when fields are blank. Expected results: ---------------- CFME should not allow a user to add a Trusted forest entry even when fields are blank. Additional info: ----------------
https://github.com/ManageIQ/manageiq/pull/1708
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/9a4b554c952faf37dfc66b475c5b24beaf48f93c commit 9a4b554c952faf37dfc66b475c5b24beaf48f93c Author: Milan Zazrivec <mzazrivec> AuthorDate: Mon Feb 16 15:24:39 2015 +0100 Commit: Milan Zazrivec <mzazrivec> CommitDate: Mon Feb 16 15:43:03 2015 +0100 UI: don't allow to add an empty ldap forest entry The LDAP hostname has to be set -- we cannot be adding a new forest entry without an LDAP hostname to the set of existing LDAP hosts. https://bugzilla.redhat.com/show_bug.cgi?id=1177015 vmdb/app/controllers/ops_controller/settings.rb | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
Verified that this issue doesn't occur in master.20150306140042_57a1769
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://rhn.redhat.com/errata/RHBA-2015-1100.html