Bug 488900

Summary: Document standard IPA input format
Product: [Retired] freeIPA Reporter: David O'Brien <daobrien>
Component: DocumentationAssignee: David O'Brien <daobrien>
Status: CLOSED DUPLICATE QA Contact: Chandrasekar Kannan <ckannan>
Severity: low Docs Contact:
Priority: low    
Version: 2.0CC: benl, dpal, jgalipea, pzuna
Target Milestone: future releaseKeywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-15 01:54:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 431020, 431022, 489811, 646217    

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 ***