IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2025-02-25 18:55:28 -06:00
Code Issues Packages Projects Releases Wiki Activity
5106421961
freeipa/install
History
Tomas Babej 5106421961 Revert "Hide topology and domainlevel features" 
This reverts commit 62e8002bc4.

Hiding of the topology and domainlevel features was necessary
for the 4.2 branch only.

Reviewed-By: Simo Sorce <ssorce@redhat.com>
2015-07-10 15:26:50 +02:00
..
certmonger plugable: Pass API to plugins on initialization rather than using set_api 2015-07-01 13:05:30 +00: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: 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
oddjob trust: support retrieving POSIX IDs with one-way trust during trust-add 2015-07-08 01:56:52 +02:00
po l10n: Update translation strings 2015-07-07 12:07:15 +02:00
restart_scripts plugable: Pass API to plugins on initialization rather than using set_api 2015-07-01 13:05:30 +00:00
share Added vault access control. 2015-07-08 06:30:23 +00:00
tools ipa-adtrust-install: allow configuring of trust agents 2015-07-08 01:56:52 +02:00
ui Revert "Hide topology and domainlevel features" 2015-07-10 15:26:50 +02:00
updates upgrade: Enable and start oddjobd if adtrust is available 2015-07-08 17:14:56 +02:00
wsgi Remove trivial path constants from modules 2014-11-04 12:57:01 +01: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.