Bug 488900 - Document standard IPA input format
Summary: Document standard IPA input format
Keywords:
Status: CLOSED DUPLICATE of bug 488891
Alias: None
Product: freeIPA
Classification: Retired
Component: Documentation
Version: 2.0
Hardware: All
OS: Linux
low
low
Target Milestone: future release
Assignee: David O'Brien
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks: 431020 freeipa20 489811 646217
TreeView+ depends on / blocked
 
Reported: 2009-03-06 05:08 UTC by David O'Brien
Modified: 2015-01-04 23:37 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-09-15 01:54:23 UTC
Embargoed:

Attachments (Terms of Use)

Description David O'Brien 2009-03-06 05:08:14 UTC 
Description of problem:


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


Additional info:
if a customer wishes to migrate data from a directory that uses non-standard schema or layout they will need to export their data and map it into this input format.

I don't expect this to be extensive, but I don't know
Comment 2 David O'Brien 2010-02-01 04:01:06 UTC 
afaik this is handled by scripts and is part of the migration effort, is that right?
Comment 4 Pavel Zuna 2010-02-01 15:23:29 UTC 
As long as users have the 'person' objectClass and groups have the 'groupOfUniqueNames' objectClass, everything should go fine with no additional work. Users only need to import their custom objectClasses and attributes to the IPA schema if they want to continue using them. Honestly, we only tested migration on DS with the default schema. If someone would provide me with a custom schema, I'll do more tests. In any case, search filters and handlers for objects being migrated can be customized easily, although it required some programming skills.
Comment 7 David O'Brien 2010-09-15 01:54:23 UTC 

*** This bug has been marked as a duplicate of bug 488891 ***
Note You need to log in before you can comment on or make changes to this bug.