freeipa/install
Petr Spacek 3cf80e747d adtrust-install: Mention AD GC port 3286 in list of required ports.
Port name "msft-gc" is taken form /etc/services file provided by package
setup-2.10.1-1.fc24.noarch.

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

Reviewed-By: Alexander Bokovoy <abokovoy@redhat.com>
2016-08-22 12:30:01 +02:00
..
certmonger ipa-certupdate: track lightweight CA certificates 2016-06-29 08:52:29 +02:00
conf mod_auth_gssapi: enable unique credential caches names 2016-06-24 16:06:49 +02:00
ffextension webui: append network.negotiate-auth.trusted-uris 2014-09-11 09:41:51 +02:00
html Added warning to user for Internet Explorer 2016-04-28 14:28:11 +02:00
migration Remove unused imports 2015-12-23 07:59:22 +01:00
oddjob Use server API in com.redhat.idm.trust-fetch-domains oddjob helper 2016-07-19 14:11:39 +02:00
po IPA 4.4.0 Translations 2016-07-01 11:24:53 +02:00
restart_scripts Update lightweight CA serial after renewal 2016-06-29 08:52:29 +02:00
share support schema files from third-party plugins 2016-08-19 15:34:26 +02:00
tools adtrust-install: Mention AD GC port 3286 in list of required ports. 2016-08-22 12:30:01 +02:00
ui Add 'trusted to auth as user' checkbox 2016-08-17 16:41:38 +02:00
updates Create indexes for krbCanonicalName attribute 2016-07-27 19:25:29 +02:00
wsgi Modernize 'except' clauses 2015-08-12 18:17:23 +02:00
configure.ac support schema files from third-party plugins 2016-08-19 15:34:26 +02:00
Makefile.am trusts: add support for one-way trust and switch to it by default 2015-07-08 01:56:52 +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.