freeipa/install
Martin Kosek aece880d8f Fix ipa-dns-install
When DNS plugin is installed via ipa-dns-install and user has a valid
Kerberos ticket at the time, the DNS installation is corrupt and named
won't start, reporting Preauthentication error.

When the non-DM identity is used for authentication, krbprincipalkey
attribute in DNS service LDAP record is not created, thus leading
to the error. This patch makes sure that authentication with Directory
Manager password is used every time.

https://fedorahosted.org/freeipa/ticket/1483
2011-07-15 17:36:29 +02:00
..
conf rename static to ui 2011-01-20 14:12:47 +00:00
html HBAC deny warning 2011-07-06 21:52:00 +00:00
migration Removed FreeWay font files. 2011-06-20 12:59:05 -04:00
po Make dogtag an optional (and default un-) installed component in a replica. 2011-06-23 19:04:33 -04:00
share Disallow direct modifications to enrolledBy. 2011-07-14 19:11:49 -04:00
tools Fix ipa-dns-install 2011-07-15 17:36:29 +02:00
ui Fixed label capitalization 2011-07-14 11:44:48 -04:00
updates Disallow direct modifications to enrolledBy. 2011-07-14 19:11:49 -04:00
configure.ac rename static to ui 2011-01-20 14:12:47 +00:00
Makefile.am rename static to ui 2011-01-20 14:12:47 +00: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.