freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2025-02-14 01:13:58 -06:00

History

Simo Sorce 2028695d88 Use wrapper for sasl gssapi binds so it behaves like other binds By calling directly sasl_interactive_bind_s() we were not calling __lateinit() This in turn resulted in some variables like dbdir not to be set on the IPAadmin object. Keep all bind types in the same place so the same common sbind steps can be performed in each case. Related to: https://fedorahosted.org/freeipa/ticket/1022		2011-03-01 11:02:55 -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	Final i18n unit test fixes.	2011-03-01 10:31:43 -05:00
share	Create default disabled sudo bind user	2011-02-23 15:32:24 -05:00
tools	Use wrapper for sasl gssapi binds so it behaves like other binds	2011-03-01 11:02:55 -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.