freeipa

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

History

Rob Crittenden 7471ba2237 Return consistent value when hostcat and usercat is all. We were returning '' for the first entry when hostcat and usercat were set to all. All subsequent entries were padded with - which effectively denied access. This requires slapi-nis 0.40+ https://fedorahosted.org/freeipa/ticket/2192		2012-04-08 16:54:32 -04:00
..
conf	Implement password based session login	2012-02-27 05:57:43 -05:00
html	Fixed inconsistent image names.	2011-10-27 14:05:12 +00:00
migration	Forms based authentication UI	2012-03-02 11:04:33 +01:00
po	Replace broken i18n shell test with Python test	2012-03-26 20:29:26 -04:00
share	Return consistent value when hostcat and usercat is all.	2012-04-08 16:54:32 -04:00
tools	Configure SELinux for httpd during upgrades	2012-04-03 18:20:51 -04:00
ui	Inter-facet expiration	2012-03-29 13:39:53 +02:00
updates	Return consistent value when hostcat and usercat is all.	2012-04-08 16:54:32 -04:00
configure.ac	Fixed rpm build warning - extension.js listed twice	2012-03-19 18:38:46 +01: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.