IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2025-02-25 18:55:28 -06:00
Code Issues Packages Projects Releases Wiki Activity
5752b35d16
freeipa/install
History
Rob Crittenden 49beb8cd3a Add missing v3 schema on upgrades, fix typo in schema. 
Add mising ipaExternalMember attribute and ipaExternalGroup objectclass.

Replacing mis-spelled ORDERING value on new install and upgrades.

https://fedorahosted.org/freeipa/ticket/3398
2013-02-22 13:30:59 +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 DN objects instead of strings 2012-08-12 16:23:24 -04:00
po Pull translation files from Transifex 2012-10-11 16:09:27 -04:00
restart_scripts Remove unused krbV imports 2013-02-01 08:13:17 +01:00
share Add missing v3 schema on upgrades, fix typo in schema. 2013-02-22 13:30:59 +01:00
tools Check SSH connection in ipa-replica-conncheck 2013-02-19 17:04:10 -05:00
ui Rename the "messages" Output of the i18n_messages command to "texts" 2013-02-21 16:26:09 +01:00
updates Add missing v3 schema on upgrades, fix typo in schema. 2013-02-22 13:30:59 +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

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.