IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-28 01:41:14 -06:00
Code Issues Packages Projects Releases Wiki Activity
979947f7f2
freeipa/install
History
Fraser Tweedale 979947f7f2 Add usercertificate attribute to user plugin 
Part of: https://fedorahosted.org/freeipa/tickets/4938

Reviewed-By: Martin Basti <mbasti@redhat.com>
2015-06-04 08:27:33 +00:00
..
certmonger Adopted kinit_keytab and kinit_password for kerberos auth 2015-04-20 08:27:35 +00:00
conf ipa-pki-proxy: provide access to profiles REST API 2015-06-04 08:27:33 +00:00
ffextension webui: append network.negotiate-auth.trusted-uris 2014-09-11 09:41:51 +02:00
html webui: remove remnants of jquery-ui 2014-06-10 10:23:22 +02:00
migration ipaplatform: Move all filesystem paths to ipaplatform.paths module 2014-06-16 19:48:20 +02:00
po Add a KRA to IPA 2014-08-22 09:59:31 +02:00
restart_scripts Adopted kinit_keytab and kinit_password for kerberos auth 2015-04-20 08:27:35 +00:00
share Add usercertificate attribute to user plugin 2015-06-04 08:27:33 +00:00
tools Import included profiles during install or upgrade 2015-06-04 08:27:33 +00:00
ui webui: datetime widget with datepicker 2015-05-20 14:36:09 +02:00
updates Add usercertificate attribute to user plugin 2015-06-04 08:27:33 +00:00
wsgi Remove trivial path constants from modules 2014-11-04 12:57:01 +01:00
configure.ac Import included profiles during install or upgrade 2015-06-04 08:27:33 +00: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

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.