freeipa/install
Alexander Bokovoy d5aa1ee04e trusts: add support for one-way trust and switch to it by default
One-way trust is the default now, use 'trust add --two-way ' to
force bidirectional trust

https://fedorahosted.org/freeipa/ticket/4959

In case of one-way trust we cannot authenticate using cross-realm TGT
against an AD DC. We have to use trusted domain object from within AD
domain and access to this object is limited to avoid compromising the whole
trust configuration.

Instead, IPA framework can call out to oddjob daemon and ask it to
run the script which can have access to the TDO object. This script
(com.redhat.idm.trust-fetch-domains) is using cifs/ipa.master principal
to retrieve TDO object credentials from IPA LDAP if needed and then
authenticate against AD DCs using the TDO object credentials.

The script pulls the trust topology out of AD DCs and updates IPA LDAP
store. Then IPA framework can pick the updated data from the IPA LDAP
under normal access conditions.

Part of https://fedorahosted.org/freeipa/ticket/4546

Reviewed-By: Tomas Babej <tbabej@redhat.com>
2015-07-08 01:56:52 +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 trusts: add support for one-way trust and switch to it by default 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 ipaVaultPublicKey attribute. 2015-07-07 07:44:56 +00:00
tools ipa-adtrust-install: allow configuring of trust agents 2015-07-08 01:56:52 +02:00
ui Hide topology and domainlevel features 2015-07-08 00:09:09 +02:00
updates Add ACI to allow hosts to add their own services 2015-06-29 13:41:52 +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

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.