Bug 1378213

Summary: Display error message when unable to lookup ldap groups
Product: Red Hat CloudForms Management Engine Reporter: Fabien CAMBI <fcambi>
Component: UI - OPSAssignee: Harpreet Kataria <hkataria>
Status: CLOSED WONTFIX QA Contact: Mike Shriver <mshriver>
Severity: low Docs Contact:
Priority: medium    
Version: 5.6.0CC: dclarizi, hkataria, jhardy, mpovolny, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: x86_64   
OS: Linux   
Whiteboard: ui:auth:miqldap:externalauth
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-20 11:54:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Fabien CAMBI 2016-09-21 20:33:14 UTC 
Description of problem:
There is no error message when the ldap lookup returns 0 groups, which makes it difficult to troubleshoot.

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

How reproducible:
Add a new group to the Access Control section, performs an ldap lookup by checking "Look Up LDAP Groups".

Steps to Reproduce:
1. Setup an openldap server missing without memberOf overlay (will result in Cloudforms not being able to list the groups of a user)
2. Configure ldap authentication on the evm server.
3. Perform a user group lookup: Settings -> Configuration -> Access Control -> CFME -> Groups -> Configuration -> Add a new Group -> Check "Look Up LDAP Groups".


Actual results:
If the request returns 0 group, there is no error message, the page simply refreshes.

Expected results:
There should be an error message saying no Groups have been found for this user.

Additional info:
Comment 4 Josh Carter 2018-09-20 11:54:51 UTC 
Bug Closure

Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!