freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2025-02-25 18:55:28 -06:00

History

Endi S. Dewata 2012f847f3 Fixed problem selecting value from combobox The IPA.combobox_widget has been modified to use the 'change' event to capture the selected value from the drop-down list. Ticket #1654		2011-08-17 18:03:29 +00:00
..
conf	rename static to ui	2011-01-20 14:12:47 +00:00
html	Fixed browser configuration pages	2011-08-17 17:28:25 +00:00
migration	Fixed broken links in ipa_error.css and ipa_migration.css.	2011-08-11 13:38:36 +00:00
po	transifex translation adjustment	2011-08-12 09:38:11 +02:00
share	Fixed browser configuration pages	2011-08-17 17:28:25 +00:00
tools	Ask for reverse DNS zone information in attended install right after asking for DNS forwarders, so that DNS configuration is done in one place.	2011-08-09 13:12:19 +02:00
ui	Fixed problem selecting value from combobox	2011-08-17 18:03:29 +00:00
updates	Correct sudo runasuser and runasgroup attributes in schema	2011-07-19 08:06:41 -04:00
configure.ac	Removed custom layouts using HTML templates.	2011-07-21 11:47:57 -04: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

README.schema

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.