IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-26 17:01:14 -06:00
Code Issues Packages Projects Releases Wiki Activity
ad2bc94725
freeipa/install
History
Petr Viktorin ad2bc94725 Use six.moves.xmlrpc.client instead of xmlrpclib 
The module is renamed to xmlrpc.client in Python 3.

Reviewed-By: David Kupka <dkupka@redhat.com>
Reviewed-By: Jan Cholasta <jcholast@redhat.com>
Reviewed-By: Martin Basti <mbasti@redhat.com>
2015-10-07 10:27:20 +02:00
..
certmonger Alias "unicode" to "str" under Python 3 2015-09-17 11:08:43 +02:00
conf Provide Kerberos over HTTP (MS-KKDCP) 2015-06-24 10:43:58 +02:00
ffextension webui: append network.negotiate-auth.trusted-uris 2014-09-11 09:41:51 +02:00
html webui: use manual Firefox configuration for Firefox >= 40 2015-09-21 12:57:25 +02:00
migration Replace dict.has_key with the 'in' operator 2015-08-12 18:17:23 +02:00
oddjob Alias "unicode" to "str" under Python 3 2015-09-17 11:08:43 +02:00
po Remove the unused pygettext script 2015-09-01 11:39:42 +02:00
restart_scripts cert renewal: Automatically update KRA agent PEM file 2015-08-27 15:53:42 +02:00
share Replace StandardError with Exception 2015-09-30 10:51:36 +02:00
tools Use six.moves.xmlrpc.client instead of xmlrpclib 2015-10-07 10:27:20 +02:00
ui webui: improve performance of search in association dialog 2015-09-30 10:42:37 +02:00
updates Limit max age of replication changelog 2015-09-21 12:04:12 +02:00
wsgi Modernize 'except' clauses 2015-08-12 18:17:23 +02:00
configure.ac trusts: add support for one-way trust and switch to it by default 2015-07-08 01:56:52 +02:00
Makefile.am trusts: add support for one-way trust and switch to it by default 2015-07-08 01:56:52 +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.