freeipa/install
Martin Babinsky 41ca3fb499 ipa-dns-install: use STARTTLS to connect to DS
BindInstance et al. now use STARTTLS to set up secure connection to DS during
ipa-dns-install. This fixes https://fedorahosted.org/freeipa/ticket/4933

Reviewed-By: Martin Basti <mbasti@redhat.com>
2015-03-18 12:32:57 +01:00
..
certmonger Make certificate renewal process synchronized 2015-01-13 18:36:10 +00:00
conf Add /session/token_sync POST support 2014-06-26 15:55:24 +02: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 Update translations 2014-07-07 16:05:21 +02:00
restart_scripts Make certificate renewal process synchronized 2015-01-13 18:36:10 +00:00
share Remove references to GPL v2.0 license 2015-02-20 15:40:42 +01:00
tools ipa-dns-install: use STARTTLS to connect to DS 2015-03-18 12:32:57 +01:00
ui webui: increase duration of notification messages 2014-12-09 12:59:32 +01:00
updates Limit deadlocks between DS plugin DNA and slapi-nis 2015-03-05 13:34:25 +00:00
wsgi ipaplatform: Move all filesystem paths to ipaplatform.paths module 2014-06-16 19:48:20 +02: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

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.