freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-28 18:01:23 -06:00

History

Endi S. Dewata a7f9814ab7 Read-only association facet. The IPA.association_facet has been modified to take a read_only parameters. If the parameter is set to true, the Enroll and Delete buttons will not be shown. All facets under the memberindirect and memberofindirect facet groups are marked as read-only. Ticket #1030		2011-05-16 21:05:49 -04:00
..
conf	rename static to ui	2011-01-20 14:12:47 +00:00
html	error handling style	2011-01-25 16:47:09 -05:00
migration	Use ldapi: instead of unsecured ldap: in ipa core tools.	2011-03-03 14:04:34 -05:00
po	Several improvements of the lint script.	2011-05-05 11:54:07 +02:00
share	Wait for memberof task and DS to start before proceeding in installation.	2011-04-22 11:43:50 +02:00
tools	Running ipa-replica-manage as non-root cause errors	2011-05-13 13:27:04 +02:00
ui	Read-only association facet.	2011-05-16 21:05:49 -04:00
updates	The default groups we create should have ipaUniqueId set	2011-04-15 13:02:17 +02:00
configure.ac	rename static to ui	2011-01-20 14:12:47 +00: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.