freeipa/install
Martin Babinsky 807702c986 Create indexes for krbCanonicalName attribute
krbCanonicalName is for a long time among the attributes guarded by uniqueness
plugins, but there was never an index for it. Now that the attribute is really
used to store canonical principal names we need to add index for it to avoid
performance regressions.

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

Reviewed-By: Thierry Bordaz <tbordaz@redhat.com>
2016-07-27 19:25:29 +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 Create indexes for krbCanonicalName attribute 2016-07-27 19:25:29 +02:00
tools unite log file name of ipa-ca-install 2016-07-21 18:37:05 +02:00
ui Close host adder dialog before showing 4304 dialog 2016-07-27 19:17:02 +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 CONFIGURE: Replace obsolete macros 2016-03-08 20:02:27 +01: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.