Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1159816 - ignoring user attributes in migrate-ds does not work if uppercase characters are returned by ldap
ignoring user attributes in migrate-ds does not work if uppercase characters ...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa (Show other bugs)
7.1
x86_64 Linux
medium Severity high
: rc
: ---
Assigned To: IPA Maintainers
Namita Soman
:
Depends On: 1150040
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-03 07:18 EST by Martin Kosek
Modified: 2015-03-05 05:14 EST (History)
11 users (show)

See Also:
Fixed In Version: ipa-4.1.0-8.el7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1150040
Environment:
Last Closed: 2015-03-05 05:14:19 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
steps with console output (5.38 KB, text/plain)
2015-01-13 08:21 EST, Kaleem
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0442 normal SHIPPED_LIVE Moderate: ipa security, bug fix, and enhancement update 2015-03-05 09:50:39 EST

  None (edit)
Description Martin Kosek 2014-11-03 07:18:51 EST
+++ This bug was initially created as a clone of Bug #1150040 +++

Description of problem:
I tried to migrate a openldap based directory to FreeIPA, while removing several objectclasses. --user-ignore-attribute didn't work.

The Problem seems to be, that the LDAPEntry Object entry_attry in migration.py isn't lowercased while the blacklist is force to lower case by the script.

the problem can be resolved by replacing
        if attr in attr_blacklist:
with:
        if attr.lower() in attr_blacklist:

Version-Release number of selected component (if applicable): 4.0.3 on Fedora 20


How reproducible: use migrate-ds with --user-ignore-attribute

Steps to Reproduce:
1. 
2.
3.

Actual results:

error:
Failed user:
  xxx: attribute "shadowLastChange" not allowed
  xxx: attribute "shadowLastChange" not allowed


Expected results:
user is migrated


Additional info:

--- Additional comment from Martin Kosek on 2014-10-07 06:59:28 EDT ---

Thanks for the bug report! I will clone it to upstream Trac. The change looks OK, would you consider sending it in form of a patch to freeipa-devel list? This way, your contribute could be recognized in FreeIPA git repository!

http://www.freeipa.org/page/Contribute/Code

--- Additional comment from Martin Kosek on 2014-10-07 06:59:57 EDT ---

Upstream ticket:
https://fedorahosted.org/freeipa/ticket/4620
Comment 3 Kaleem 2015-01-12 03:38:54 EST
How to verify this?
Comment 4 Martin Kosek 2015-01-12 07:20:28 EST
As noted in the description, you would need to setup Directory Server which returns attributes with mixed case (like OpenLDAP) and try to run migrate-ds and blacklist some mixed-case attribute.

Jan, do you know about an easier change with 389 DS how to reproduce this issue?
Comment 5 Jan Cholasta 2015-01-12 07:29:21 EST
Maybe install IPA A, look for mixed-case attribute names in "ipa user-find --all --raw" output, run migrate-ds on IPA B from IPA A and blacklist some of the mixed-case attributes. Or you can add some custom user schema to IPA A and set a mixed-case attribute on a user before migrating.
Comment 6 Kaleem 2015-01-13 08:21:38 EST
Created attachment 979619 [details]
steps with console output

Verified.

[root@vm-idm-004 ~]# rpm -q ipa-server
ipa-server-4.1.0-13.el7.x86_64
[root@vm-idm-004 ~]# 

Please find the attached verification steps along with console output.
Comment 8 errata-xmlrpc 2015-03-05 05:14:19 EST
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/RHSA-2015-0442.html

Note You need to log in before you can comment on or make changes to this bug.