freeipa/install
Petr Viktorin 91606e6679 Change DNA magic value to -1 to make UID 999 usable
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
2013-03-11 17:07:07 +01:00
..
certmonger Remove unused krbV imports 2013-02-01 08:13:17 +01:00
conf Enable mod_deflate 2013-01-17 17:19:29 +01:00
ffextension Kerberos authentication extension makefiles 2012-10-04 18:07:34 -04:00
html Move of Web UI non AMD dep. libs to libs subdirectory 2013-01-18 15:10:36 +01:00
migration Use IPAdmin rather than raw python-ldap in migration.bind 2013-03-01 16:59:46 +01:00
po Pull translation files from Transifex 2012-10-11 16:09:27 -04:00
restart_scripts Remove support for DN normalization from LDAPClient. 2013-03-01 16:59:47 +01:00
share Change DNA magic value to -1 to make UID 999 usable 2013-03-11 17:07:07 +01:00
tools Fix installing server with external CA 2013-03-08 15:42:20 +01:00
ui Allow 'nfs:NONE' in global configuration 2013-03-08 10:46:00 +01:00
updates Change DNA magic value to -1 to make UID 999 usable 2013-03-11 17:07:07 +01:00
configure.ac Updated makefiles to build FreeIPA Web UI layer 2013-01-18 15:10:37 +01:00
Makefile.am Move CRL publish directory to IPA owned directory 2012-10-09 16:00:01 +02:00
README.schema Add some basic rules for adding new schema 2010-08-27 13:40:37 -04:00

Ground rules on adding new schema

Brand new schema, particularly when written specifically for IPA, should be
added in share/*.ldif. Any new files need to be explicitly loaded in
ipaserver/install/dsinstance.py. These simply get copied directly into
the new instance schema directory.

Existing schema (e.g. in an LDAP draft) may either be added as a separate
ldif in share or as an update in the updates directory. The advantage of
adding the schema as an update is if 389-ds ever adds the schema then the
installation won't fail due to existing schema failing to load during
bootstrap.

If the new schema requires a new container then this should be added
to install/bootstrap-template.ldif.