freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-30 10:47:08 -06:00

History

Endi S. Dewata 5eba2ffddd Fixed tab and dialog widths. The width of the 1st level tab has been modified to expand according to the size of the tab label. The width of the adder dialogs have been increased to allow longer button labels. Ticket #1825		2011-09-29 16:56:54 +00:00
..
conf	Revert "Always require SSL in the Kerberos authorization block."	2011-09-27 08:54:42 +02: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	25 Create Tool for Enabling/Disabling Managed Entry Plugins	2011-09-21 09:22:13 +02:00
share	Fix typo in v3 base schema	2011-09-21 08:29:58 -04:00
tools	Detect CA installation type in ipa-replica-prepare and ipa-ca-install.	2011-09-27 17:50:46 +02:00
ui	Fixed tab and dialog widths.	2011-09-29 16:56:54 +00:00
updates	The precendence on the modrdn plugin was set in the wrong location.	2011-09-13 17:36:59 +02:00
configure.ac	ticket 1650 - compute accurate translation statistics	2011-08-18 14:25:58 +02: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.