freeipa/install
Alexander Bokovoy e88049ecee ipasam: improve SASL bind callback
SASL bind callback due to refactoring was referencing local variable which
didn't exist all the time. Fix that by including a copy of service principals
into ipasam long term private struct.

Rework ccache handling to avoid re-initing every time callback is called
2012-07-06 13:06:15 +03:00
..
conf Fix compatibility with Fedora 18. 2012-07-02 15:20:13 +02: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 validate i18n strings when running "make lint" 2012-04-26 13:53:37 +02:00
restart_scripts Configure certmonger to execute restart scripts on renewal. 2012-04-10 01:08:41 -04:00
share ipasam: improve SASL bind callback 2012-07-06 13:06:15 +03:00
tools Centralize timeout for waiting for servers to start. 2012-07-02 17:08:58 -04:00
ui Continuation of removing of not supported command options from Web UI 2012-06-29 11:56:29 +02:00
updates Create default range entry after upgrade 2012-07-02 16:27:33 +02:00
configure.ac Configure certmonger to execute restart scripts on renewal. 2012-04-10 01:08:41 -04:00
Makefile.am Add sysupgrade state file 2012-06-10 21:23:10 -04:00
README.schema Add some basic rules for adding new schema 2010-08-27 13:40:37 -04:00

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.