freeipa

0 Fork 0

Files

T

Martin Babinsky ff7969852d load RA backend plugins during standalone CA install on CA-less IPA master

CA-less IPA master has 'ra_plugin' set to 'none' in IPA config. When setting
up Dogtag CA on the master we must override this setting in order to load
dogtag backend plugins and succesfully complete CA installation.

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

Reviewed-By: Jan Cholasta <jcholast@redhat.com>

2015-09-09 08:21:32 +02:00

certmonger

Use the print function

2015-09-01 11:42:01 +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: add Kerberos configuration instructions for Chrome

2015-07-27 13:50:49 +02:00

migration

Replace dict.has_key with the 'in' operator

2015-08-12 18:17:23 +02:00

oddjob

Decode script arguments using file system encoding

2015-09-07 08:00:11 +02:00

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

Added CLI param and ACL for vault service operations.

2015-08-17 08:10:59 +02:00

tools

load RA backend plugins during standalone CA install on CA-less IPA master

2015-09-09 08:21:32 +02:00

webui: add option to establish bidirectional trust

2015-08-26 13:05:51 +02:00

updates

trusts: harden trust-fetch-domains oddjobd-based script

2015-08-18 18:48: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.