Bug 2175852

Summary:	[doc] Add consideration about user UIDs migrated from LDAP to IPA may end up being ouside IPA ID ranges
Product:	Red Hat Enterprise Linux 8	Reporter:	Aleksandr Sharov <asharov>
Component:	Documentation	Assignee:	David Voženílek <dvozenil>
Documentation sub component:	default	QA Contact:	RHEL DPM <rhel-docs>
Status:	ASSIGNED ---	Docs Contact:
Severity:	unspecified
Priority:	high	CC:	rhel-docs
Version:	8.0	Keywords:	Documentation
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Aleksandr Sharov 2023-03-06 16:08:50 UTC

Document URL: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/migrating_to_identity_management_on_rhel_8/index#considerations-in-migrating-from-ldap-to-idm_migrating-from-an-ldap-directory-to-idm

Section Number and Name: 4.1. Considerations in migrating from LDAP to IdM

Describe the issue: This part doesn't describe how migrated UIDs and GIDs end up over IDM IDranges that existed previously, and what happens if conflict arises during migration

Suggestions for improvement: Add considerations regarding checking:
- That no UID/GID will intersect with already existing in IPA;
- That all migrated users and groups will end up inside IPA idrange. If needed, they should create new IDrange to accommodate new entities.

Additional information: -