freeipa

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

History

Alexander Bokovoy b93e0b8bbf Convert nsaccountlock to always work as bool towards Python code https://fedorahosted.org/freeipa/ticket/1259 Python code will see nsaccountlock as bool. JavaScript code will also see it as bool. This allows native boolean operations with the lock field. Passes both CLI and WebUI tests.		2011-07-13 12:02:46 +02:00
..
conf	rename static to ui	2011-01-20 14:12:47 +00:00
html	HBAC deny warning	2011-07-06 21:52:00 +00:00
migration	Removed FreeWay font files.	2011-06-20 12:59:05 -04:00
po	Make dogtag an optional (and default un-) installed component in a replica.	2011-06-23 19:04:33 -04:00
share	Remove redundant configuration values from krb5.conf.	2011-06-28 01:10:06 -04:00
tools	Verify that the hostname is fully-qualified before accessing the service information in ipactl.	2011-06-24 01:23:14 -04:00
ui	Convert nsaccountlock to always work as bool towards Python code	2011-07-13 12:02:46 +02:00
updates	Configure Managed Entries on replicas.	2011-05-25 16:39:27 -04: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.