freeipa/install
Lynn Root c481e40d78 Fixed the catch of the hostname option during ipa-server-install
Originally ipa-server-install would still prompt for the hostname even if it's supplied in the initial installation command.

Ticket: https://fedorahosted.org/freeipa/ticket/2692
2012-12-11 11:04:02 +01:00
..
certmonger Use DN objects instead of strings 2012-08-12 16:23:24 -04:00
conf Configure the initial CA as the CRL generator. 2012-10-09 19:24:43 -04:00
ffextension Kerberos authentication extension makefiles 2012-10-04 18:07:34 -04:00
html Removal of delegation-uris instruction from browser config 2012-10-04 18:35:47 -04:00
migration Use DN objects instead of strings 2012-08-12 16:23:24 -04:00
po Pull translation files from Transifex 2012-10-11 16:09:27 -04:00
restart_scripts Wait for the directory server to come up when updating the agent certificate. 2012-11-01 13:36:52 -04:00
share Add OCSP and CRL URIs to certificates 2012-12-07 11:00:17 -05:00
tools Fixed the catch of the hostname option during ipa-server-install 2012-12-11 11:04:02 +01:00
ui Better error message for login of users from other realms 2012-12-06 17:02:03 +01:00
updates Enable transactions by default, make password and modrdn TXN-aware 2012-11-21 14:55:12 +01:00
configure.ac Kerberos authentication extension makefiles 2012-10-04 18:07:34 -04:00
Makefile.am Move CRL publish directory to IPA owned directory 2012-10-09 16:00:01 +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.