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.
Commit https://pagure.io/freeipa/c/5be9341fbabaf7bcb396a2ce40f17e1ccfa54b77 added additional security checks to protect password bind (simple bind). The check prohibit to send the password unencrypted over a clear text line.
Temporary workaround: Use ipa migrate-ds with a ldaps:// URL when possible.
I'll work on a patch that allows to use insecure connections for migration.
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/RHBA-2019:3348
Description of problem: ipa migrate-ds fails with internal error. Version-Release number of selected component (if applicable): ipa-server-4.8.0-4.module+el8.1.0+3696+eb4a1e69.x86_64 How reproducible: Always Steps to Reproduce: 1. Install IPA server 2. Run ipa migrate-ds command Actual results: Internal error is seen. [Mon Jul 22 18:07:33.180155 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] ipa: DEBUG: migrate_ds('ldap://master.rhel81.test:3389', '********', binddn=ipapython.dn.DN('cn=directory manager'), usercontainer=ipapython.dn.DN('ou=People'), groupcontainer=ipapython.dn.DN('ou=groups'), userobjectclass=('person',), groupobjectclass=('groupOfUniqueNames', 'groupOfNames'), userignoreobjectclass=None, userignoreattribute=None, groupignoreobjectclass=None, groupignoreattribute=None, groupoverwritegid=False, schema='RFC2307bis', continue=False, compat=True, use_def_group=True, scope='onelevel', version='2.233', exclude_users=None, exclude_groups=None) [Mon Jul 22 18:07:33.182543 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] ipa: DEBUG: retrieving schema for SchemaCache url=ldapi://%2Fvar%2Frun%2Fslapd-RHEL81-TEST.socket conn=<ldap.ldapobject.SimpleLDAPObject object at 0x7efcdbed69e8> [Mon Jul 22 18:07:33.393732 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] ipa: ERROR: non-public: ValueError: simple_bind over insecure LDAP connection [Mon Jul 22 18:07:33.393752 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] Traceback (most recent call last): [Mon Jul 22 18:07:33.393758 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] File "/usr/lib/python3.6/site-packages/ipaserver/rpcserver.py", line 368, in wsgi_execute [Mon Jul 22 18:07:33.393763 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] result = command(*args, **options) [Mon Jul 22 18:07:33.393768 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] File "/usr/lib/python3.6/site-packages/ipalib/frontend.py", line 450, in __call__ [Mon Jul 22 18:07:33.393774 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] return self.__do_call(*args, **options) [Mon Jul 22 18:07:33.393779 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] File "/usr/lib/python3.6/site-packages/ipalib/frontend.py", line 478, in __do_call [Mon Jul 22 18:07:33.393784 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] ret = self.run(*args, **options) [Mon Jul 22 18:07:33.393789 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] File "/usr/lib/python3.6/site-packages/ipalib/frontend.py", line 800, in run [Mon Jul 22 18:07:33.393794 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] return self.execute(*args, **options) [Mon Jul 22 18:07:33.393799 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] File "/usr/lib/python3.6/site-packages/ipaserver/plugins/migration.py", line 917, in execute [Mon Jul 22 18:07:33.393804 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] ds_ldap.simple_bind(options['binddn'], bindpw) [Mon Jul 22 18:07:33.393809 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] File "/usr/lib/python3.6/site-packages/ipapython/ipaldap.py", line 1215, in simple_bind [Mon Jul 22 18:07:33.393814 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] raise ValueError('simple_bind over insecure LDAP connection') [Mon Jul 22 18:07:33.393822 2019] [wsgi:error] [pid 28555:tid 139624469780224] [remote 10.65.206.140:47746] ValueError: simple_bind over insecure LDAP connection Expected results: The command should execute without any error. Additional info: