freeipa/install
Petr Vobornik 65bde3ecd7 webui: use unique ids for checkboxes
Checkboxes have not used unique ids across the whole UI. It broke checking by clicking on label for later displayed instances. It became serious problem when rcue introduced new checkbox styles with 'label clicking' as default check method.

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

Reviewed-By: Adam Misnyovszki <amisnyov@redhat.com>
2014-03-13 11:10:42 +01:00
..
certmonger Log unhandled exceptions in certificate renewal scripts. 2014-03-10 18:41:10 +01:00
conf Use only system fonts 2014-01-21 12:05:09 +01:00
ffextension Kerberos authentication extension makefiles 2012-10-04 18:07:34 -04:00
html Load updated Web UI files after server upgrade 2013-10-16 18:06:30 +02:00
migration Use IPAdmin rather than raw python-ldap in migration.py and ipadiscovery.py 2013-03-13 12:36:33 +01:00
po Use /usr/bin/python2 2014-01-03 09:46:05 +01:00
restart_scripts Log unhandled exceptions in certificate renewal scripts. 2014-03-10 18:41:10 +01:00
share Make all ipatokenTOTP attributes mandatory 2014-02-21 16:07:39 +01:00
tools ipa-replica-install never checks for 7389 port 2014-03-11 17:10:28 +01:00
ui webui: use unique ids for checkboxes 2014-03-13 11:10:42 +01:00
updates Add HOTP support 2014-02-21 10:26:02 +01:00
wsgi Generate plugin index dynamically 2013-05-06 16:22:30 +02:00
configure.ac RCUE initial commit 2014-01-21 12:04:02 +01:00
Makefile.am Change group ownership of CRL publish directory 2013-07-16 12:17:40 +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.