Bug 1579986
| Summary: | LDAP user can log into one region and not the other | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Tuan <tuado> |
| Component: | Appliance | Assignee: | Joe Vlcek <jvlcek> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Matt Pusateri <mpusater> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.8.0 | CC: | abellott, cpelland, gtanzill, hkataria, jprause, jvlcek, lavenel, mpovolny, mpusater, obarenbo, tuado, yrudman |
| Target Milestone: | GA | ||
| Target Release: | 5.8.5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | auth:miqldap:ad | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-08-07 15:43:52 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | Bug | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | CFME Core | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1572700 | ||
|
Comment 3
Joe Vlcek
2018-05-22 18:48:01 UTC
Tuan, Please extend my thanks to the customer for all the help and patience with this issue. After reviewing the provided data I am fairly sure I realize what is happening. In the 4.2 appliance there was a bug that was fixed in the newer versions. Groups should be manually created in every region but the bug was that groups would match across regions. So groups only had to be manually created in one region. The fix plugged this issue by confirming that the user attempting to log in had matching groups manually created in the region they are logging into. The new functionality checks that groups were manually created in every region you want those users to log into. Please test by manually adding the groups for one user to one region that is failing. If this does not resolve the problem, let's try to setup a conference call to diagnose this directly some time Tuesday or later next week. Taun, Please also ask them to time how long the ldapsearch command takes on both of the system. They should take about the same time on both. e.g.: time ldapsearch -x -H ldaps://ldaphost.example.com:636 -b "dc=example,dc=com" Thank you. Joe Taun, I noticed the customer has not updated the case with the output from "time" on the ldapsearch commands. Since the last update the customer states that the failures are observed on both their 4.5 and and 4.2 environments a likely issues could be LDAP performance related. Upon reexamining the data they have already provided I see they have "group_memberships_max_depth" set to "10". This deep of a group membership search could produce performance issues. I also noticed they have configured two LDAP servers. It would be best if they could do some experimenting with using only one at a time to eliminate the possibility that one server is having performance issues. Please ask them to provide the output from a command similar to the one below run on both regions and to both of their LDAP servers: time ldapsearch -x -LLL -H ldaps://<my ldap server>:636 -b "<my searchbase>" -D "<my binddn?" -w <my password> -s sub "(userPrincipalName=<my user>@<my user suffix>)" '*' memberof Please pass this comment on "as is" directly to the customers. I am also available for a video conf call if needed. JoeV Tuan, Please also ask Ben to provide the debugging data as described in comment 17 https://bugzilla.redhat.com/show_bug.cgi?id=1579986#c17 To enable debugging for Authentication please set `:level:` under section `:log:` in the `Configuration/Settings/Advanced` to `debug` the tail the evm.log file while attempting to log in with the failing user ID. You should see line with: MiqLdap#... and Authenticator::Ldap#... Thank you, JoeV The customer reports things work fine for some users but users with many more groups are seeing various failures. This indicates to me that the issue is very likely routed in the customers environment. I have offered many times to join a conf call to help diagnose and root cause the issue but the customers seems reluctant to do that. II propose this case be downgraded or closed. JoeV Tuan, This BZ has been in "Waiting on Customer" status for many weeks now. The description of the problem has also changed during the course of time this bug has been open, making it hard to understand what is wrong. I'm going to mark it closed/insufficient_data. If the customer wishes to reopen please ask them if we can get on a video conference to see what is failing and diagnose the issue. Thank you. JoeV Closed. Canceling NEEDINFO |