freeipa/install
Ana Krivokapic afbf528a83 WebUI: Add userClass attribute to user and host pages
Add userClass attribute to:
- user and host adder dialogs
- user and host detail facets

Design page: http://www.freeipa.org/page/V3/Integration_with_a_provisioning_systems
https://fedorahosted.org/freeipa/ticket/3590
2013-11-19 14:27:50 +01:00
..
certmonger Remove unused krbV imports 2013-02-01 08:13:17 +01:00
conf Load updated Web UI files after server upgrade 2013-10-16 18:06:30 +02:00
ffextension Kerberos authentication extension makefiles 2012-10-04 18:07:34 -04:00
html Load updated Web UI files after server upgrade 2013-10-16 18:06:30 +02:00
migration Use IPAdmin rather than raw python-ldap in migration.py and ipadiscovery.py 2013-03-13 12:36:33 +01:00
po Update translations from Transifex 2013-10-04 14:51:19 +02:00
restart_scripts Make CS.cfg edits with CA instance stopped 2013-08-26 16:21:36 +02:00
share Add userClass attribute for users 2013-11-19 14:27:50 +01:00
tools Update the man page for ipa-ldap-updater 2013-11-18 16:54:21 +01:00
ui WebUI: Add userClass attribute to user and host pages 2013-11-19 14:27:50 +01:00
updates Remove schema modifications from update files 2013-11-18 16:54:21 +01:00
wsgi Generate plugin index dynamically 2013-05-06 16:22:30 +02:00
configure.ac Prevent *.pyo and *.pyc multilib problems 2013-08-13 15:31:46 +02:00
Makefile.am Change group ownership of CRL publish directory 2013-07-16 12:17:40 +02: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.