freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2025-02-16 18:35:01 -06:00

History

Jr Aquino 1770750b8a Create default disabled sudo bind user Read access is denied to the sudo container for unauthenticated users. This shared user can be used to provide authenticated access to the sudo information. https://fedorahosted.org/freeipa/ticket/998		2011-02-23 15:32:24 -05: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	Fix migration page	2011-02-11 13:28:22 -05:00
po	Update Polish & Ukrainian translations	2011-02-18 10:30:32 -05:00
share	Create default disabled sudo bind user	2011-02-23 15:32:24 -05:00
tools	Fixed in ipa-server-install help and man page	2011-02-18 10:00:48 -05:00
ui	splitting banner requires new file in Makefile.am	2011-02-23 11:23:16 -05:00
updates	Add default roles and permissions for HBAC, SUDO and pw policy	2011-02-22 10:02:24 -05: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.