IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-26 00:41:25 -06:00
Code Issues Packages Projects Releases Wiki Activity
af0a2409f9
freeipa/install
History
Jan Cholasta fe4b3190e9 Revert "Make all ipatokenTOTP attributes mandatory" 
This prevents schema replication conflicts which cause replication failures
with older versions of IPA. Details in
https://bugzilla.redhat.com/show_bug.cgi?id=1176995#c7

This reverts commit adcd373931.

https://fedorahosted.org/freeipa/ticket/4833

Reviewed-By: Martin Kosek <mkosek@redhat.com>
2015-01-21 09:20:15 +01:00
..
certmonger Make certificate renewal process synchronized 2015-01-13 18:34:59 +00:00
conf Fixed KRA backend. 2014-11-04 16:33:16 +01:00
ffextension webui: append network.negotiate-auth.trusted-uris 2014-09-11 09:41:51 +02:00
html webui: remove remnants of jquery-ui 2014-06-10 10:23:22 +02:00
migration ipaplatform: Move all filesystem paths to ipaplatform.paths module 2014-06-16 19:48:20 +02:00
po Add a KRA to IPA 2014-08-22 09:59:31 +02:00
restart_scripts Make certificate renewal process synchronized 2015-01-13 18:34:59 +00:00
share Revert "Make all ipatokenTOTP attributes mandatory" 2015-01-21 09:20:15 +01:00
tools Fix validation of ipa-restore options 2015-01-14 09:10:06 +01:00
ui webui: increase duration of notification messages 2014-12-09 12:59:32 +01:00
updates Replication Administrators cannot remove replication agreements 2015-01-20 16:52:53 +01:00
wsgi Remove trivial path constants from modules 2014-11-04 12:57:01 +01:00
configure.ac RCUE initial commit 2014-01-21 12:04:02 +01: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.