freeipa

0 Fork 0

Files

T

Martin Basti 4006cbbc02 KRA: add --setup-kra to ipa-server-install

This patch allows to install KRA on first IPA server in one step using
ipa-server-install

This option improves containers installation where ipa-server can be
installed with KRA using one call without need to call docker exec.

Please note the the original `kra.install()` calls in
ipaserver/install/server/install.py were empty operations as it did
nothing, so it is safe to move them out from CA block

https://pagure.io/freeipa/issue/6731

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

2017-03-08 15:50:30 +01:00

certmonger

Moving ipaCert from HTTPD_ALIAS_DIR

2017-03-01 09:43:41 +00:00

conf

Limit sessions to 30 minutes by default

2017-03-01 13:43:40 +01:00

html

Build: remove incorrect use of MAINTAINERCLEANFILES

2016-11-16 09:12:07 +01:00

migration

Set explicit confdir option for global contexts

2016-12-02 09:14:35 +01:00

oddjob

Add a new user to run the framework code

2017-02-15 07:13:37 +01:00

restart_scripts

Moving ipaCert from HTTPD_ALIAS_DIR

2017-03-01 09:43:41 +00:00

Support for Certificate Identity Mapping

2017-03-02 15:09:42 +01:00

tools

KRA: add --setup-kra to ipa-server-install

2017-03-08 15:50:30 +01:00

WebUI: don't change casing of Auth Indicators values

2017-03-08 15:43:11 +01:00

updates

Support for Certificate Identity Mapping

2017-03-02 15:09:42 +01:00

wsgi

Build: remove incorrect use of MAINTAINERCLEANFILES

2016-11-16 09:12:07 +01:00

Makefile.am

Configure HTTPD to work via Gss-Proxy

2017-02-15 07:13:37 +01: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.