freeipa.git - FreeIPA project

	Commit message (Collapse)	Author	Age	Files	Lines
*	User Life Cycle: DNA scopes full SUFFIX	Thierry bordaz (tbordaz)	2014-09-01	1	-3/+1
\| \| \| \| \| \| \| \| \| \| \|	In patch 0001-3, the DNA plugins configuration was changed to scope only 'cn=accounts,SUFFIX' This part of the fix was invalid as trust domain object (that need uid/gid allocation) are under 'cn=trust,SUFFIX'. Revert that part of the fix. Waiting on https://fedorahosted.org/389/ticket/47828, to exclude provisioning contains https://fedorahosted.org/freeipa/ticket/3813 Reviewed-By: Martin Kosek <mkosek@redhat.com>
*	User Life Cycle: create containers and scoping DS plugins	Thierry bordaz (tbordaz)	2014-08-19	1	-1/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	User Life Cycle is designed http://www.freeipa.org/page/V4/User_Life-Cycle_Management It manages 3 containers (Staging, Active, Delete). At install/upgrade Delete and Staging containers needs to be created. Active: cn=users,cn=accounts,$SUFFIX Delete: cn=deleted users,cn=accounts,cn=provisioning,$SUFFIX Stage: cn=staged users ,cn=accounts,cn=provisioning,$SUFFIX Plugins scopes: krbPrincipalName, krbCanonicalName, ipaUniqueID, uid: cn=accounts,SUFFIX cn=deleted users,cn=accounts,cn=provisioning,SUFFIX DNA: cn=accounts,SUFFIX Plugins exclude subtree: IPA UUID, Referential Integrity, memberOf: cn=provisioning,SUFFIX https://fedorahosted.org/freeipa/ticket/3813 Reviewed-By: Petr Viktorin <pviktori@redhat.com>
*	Change DNA magic value to -1 to make UID 999 usable	Petr Viktorin	2013-03-11	1	-0/+10
\| \| \| \| \| \| \| \| \| \| \| \| \|	Change user-add's uid & gid parameters from autofill to optional. Change the DNA magic value to -1. For old clients, which will still send 999 when they want DNA assignment, translate the 999 to -1. This is done via a new capability, optional_uid_params. Tests included https://fedorahosted.org/freeipa/ticket/2886
*	Name update files so they can be easily sorted.	Rob Crittenden	2009-03-25	1	-0/+3
	We want to process some updates in a particular order (schema, structural). Using an init-inspired ordering mechanism.