IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-26 08:51:50 -06:00
Code Issues Packages Projects Releases Wiki Activity
c098435040
freeipa/install
History
Jan Cholasta 693710784b Print newline after receiving EOF in installutils.read_password.
2013-07-24 10:00:03 +02:00
..
certmonger Remove unused krbV imports 2013-02-01 08:13:17 +01:00
conf Do not redirect to https in /ipa/ui on non-HTML files 2013-06-26 15:02:13 +02:00
ffextension Kerberos authentication extension makefiles 2012-10-04 18:07:34 -04:00
html Make ssbrowser.html work in IE 10 2013-06-04 12:24:13 +02:00
migration Use IPAdmin rather than raw python-ldap in migration.py and ipadiscovery.py 2013-03-13 12:36:33 +01:00
po Make an ipa-tests package 2013-06-17 19:22:50 +02:00
restart_scripts Do actually stop pki_cad in stop_pkicad instead of starting it. 2013-04-09 16:22:23 +02:00
share Add Camellia ciphers to allowed list. 2013-07-18 10:49:38 +03:00
tools Print newline after receiving EOF in installutils.read_password. 2013-07-24 10:00:03 +02:00
ui Remove word 'field' from GECOS param label 2013-07-23 15:32:13 +02:00
updates Add Camellia ciphers to allowed list. 2013-07-18 10:49:38 +03:00
wsgi Generate plugin index dynamically 2013-05-06 16:22:30 +02:00
configure.ac Generate plugin index dynamically 2013-05-06 16:22:30 +02:00
Makefile.am Change group ownership of CRL publish directory 2013-07-16 12:17:40 +02: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.