IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2025-02-03 20:21:24 -06:00
Code Issues Packages Projects Releases Wiki Activity
20fce97dfa
freeipa/install
History
Sumit Bose b367c9ee7e Use exop instead of kadmin.local
2012-06-11 09:40:59 +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 validate i18n strings when running "make lint" 2012-04-26 13:53:37 +02:00
restart_scripts Configure certmonger to execute restart scripts on renewal. 2012-04-10 01:08:41 -04:00
share Add trust-related ACIs 2012-06-07 09:39:10 +02:00
tools Only allow root to run update plugins 2012-06-07 05:02:22 -04:00
ui Update of serverconfig ipaconfigstring options 2012-06-06 22:14:12 -04:00
updates Use exop instead of kadmin.local 2012-06-11 09:40:59 +02:00
configure.ac Configure certmonger to execute restart scripts on renewal. 2012-04-10 01:08:41 -04:00
Makefile.am Configure certmonger to execute restart scripts on renewal. 2012-04-10 01:08:41 -04: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.