freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-28 18:01:23 -06:00

History

Rob Crittenden a735420a9b Set nsslapd-minssf-exclude-rootdse to on so the DSE is always available. If minssf is set in configuration and this is not set then clients won't be able to detect the available namingContexts, defaultNamingContext, capabilities, etc. https://fedorahosted.org/freeipa/ticket/2542		2012-03-26 14:26:10 +02:00
..
conf	Implement password based session login	2012-02-27 05:57:43 -05:00
html	Fixed inconsistent image names.	2011-10-27 14:05:12 +00:00
migration	Forms based authentication UI	2012-03-02 11:04:33 +01:00
po	update translation pot file	2012-02-21 17:19:20 -05:00
share	Add support for sudoOrder	2012-03-01 21:02:33 -05:00
tools	Wait for child process to terminate after receiving SIGINT in ipautil.run.	2012-03-23 10:53:02 +01:00
ui	Typos in FreeIPA messages	2012-03-23 16:59:12 +01:00
updates	Set nsslapd-minssf-exclude-rootdse to on so the DSE is always available.	2012-03-26 14:26:10 +02:00
configure.ac	Fixed rpm build warning - extension.js listed twice	2012-03-19 18:38:46 +01:00
Makefile.am	rename static to ui	2011-01-20 14:12:47 +00:00
README.schema	Add some basic rules for adding new schema	2010-08-27 13:40:37 -04:00

README.schema

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.