freeipa/install
Endi Sukma Dewata 267e803cdf Service certificate status.
The service details page has been modified to show certificate
status using bullets. It will also show the revocation reason,
and display the restore button only if the certificate is on
hold. The buttons action handlers have been moved into
service_usercertificate_load() so they can update the bullets.

A test data file for cert-show operation has been added. Other
test data files containing certificate info has been updated for
consistency.

The certificate_confirmation_dialog() has been removed because
it's no longer used.
2010-10-18 14:22:07 -04:00
..
conf IPA HTTPD config uses /usr/share/static as target for /ipa/ui 2010-08-09 15:07:06 -04:00
html Get merged tree into an installalble state. 2009-02-03 15:29:20 -05:00
migration Add DS migration plugin and password migration page. 2010-01-20 16:54:17 -05:00
po Update Polish translation 2010-10-15 10:07:01 -04:00
share ntpdinstance: Do not replace the config files, just add needed options 2010-10-18 13:54:17 -04:00
static Service certificate status. 2010-10-18 14:22:07 -04:00
tools Include REPLICA_FILE in usage for ipa-replica-install 2010-10-13 13:01:05 -04:00
updates Use correct description in hostgroup acis. 2010-10-06 21:52:03 -04:00
configure.ac Changes to the install and config files to support deploying the javascript code. 2010-08-06 11:55:52 -04:00
Makefile.am Changes to the install and config files to support deploying the javascript code. 2010-08-06 11:55:52 -04: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.