Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionSandi Wallendahl
2020-10-29 16:22:06 UTC
Description of problem:
High login times are encountered for user accounts that are fetched from AD using the trust between IPA and AD realms, when the AD realm has lots (e.g. thousands) of user accounts.
Version-Release number of selected component (if applicable):
ipa-server 4.6.6
How reproducible:
Always
Steps to Reproduce:
1. Install and configure IPA server, use default configuration
2. Install and configure IPA client, use default configuration
3. Have a Microsoft Active Directory instance with a high amount (e.g. thousands) of users
3. Create a trust between IPA and AD and set up AD users to be able to login through the trust
4. Try to login with an AD user account
Actual results:
Login over ssh takes 5-10 seconds
Expected results:
Login should not take this long, expected login time is about one second
Additional info:
The issue is caused by ipaExternalMember entry being unindexed and can be mitigated on the IPA server-side with the following:
Create a file: 90-index-ipaExternalMember.update
--------------------------------------------------------------------------------------------
dn: cn=ipaExternalMember,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config
default: cn: ipaExternalMember
default: objectClass: top
default: objectClass: nsIndex
default: nsSystemIndex: false
default: nsIndexType: eq
--------------------------------------------------------------------------------------------
Apply it by running the following as root on all of IPA servers:
# ipa-ldap-updater ./90-index-ipaExternalMember.update
Since the version 4.6.5 of IPA there's an auto-indexing feature. So after this schema-update is put in place, IPA automatically creates a task for itself to index ipaExternalMember entries.
/var/log/ipaupgrade.log can be followed to verify the task has started:
<timestamp> DEBUG Creating task cn=indextask_<taskid>,cn=index,cn=tasks,cn=config to index attributes: ipaExternalMember
This issue has been fixed in upstream with: https://github.com/freeipa/freeipa/commit/9f0ec27e9f13ed40b8e58162d99bf9b0e8b4afd5
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 (Moderate: ipa security and bug fix update), 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-2021:0860