freeipa/install
Martin Kosek 0e432d33fc Index ipakrbprincipalalias and ipaautomountkey attributes
An unindexed search for ipakrbprincipalalias is fired for every ipa
command (and other authentication events) which would degrade IPA
server performance if not indexed. ipaautomountkey unindexed searches
are hit when new key entries are being added.

Add both indexes to new and updated IPA installs.

https://fedorahosted.org/freeipa/ticket/3020
https://fedorahosted.org/freeipa/ticket/3025
2012-10-01 22:37:59 -04:00
..
certmonger Use DN objects instead of strings 2012-08-12 16:23:24 -04:00
conf Use Dogtag 10 only when it is available 2012-09-17 18:43:59 -04:00
html Fixed inconsistent image names. 2011-10-27 14:05:12 +00:00
migration Use DN objects instead of strings 2012-08-12 16:23:24 -04:00
po Update the pot file (translation source) 2012-09-12 22:04:16 -04:00
restart_scripts Use Dogtag 10 only when it is available 2012-09-17 18:43:59 -04:00
share Index ipakrbprincipalalias and ipaautomountkey attributes 2012-10-01 22:37:59 -04:00
tools Use custom zonemgr for reverse zones 2012-09-26 13:44:11 +02:00
ui Fix integer validation when boundary value is empty string 2012-09-19 11:09:09 +02:00
updates Index ipakrbprincipalalias and ipaautomountkey attributes 2012-10-01 22:37:59 -04:00
configure.ac Use certmonger to renew CA subsystem certificates 2012-07-30 13:39:08 +02:00
Makefile.am Use certmonger to renew CA subsystem certificates 2012-07-30 13:39:08 +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.