freeipa

0 Fork 0

Files

T

Christian Heimes 25d1afdc54 Improve error handling in ipa-httpd-kdcproxy

The pre start script 'ipa-httpd-kdcproxy' for httpd.service now handles
connection and authentication errors more gracefully. If the script is
not able to conenct to LDAP, it only prints a warning and exits with
status code 0. All other errors are still reported as fatal error and
result in a non-zero exit code.

This fixes a problem with offline RPM updates. A restart of Apache no
longer fails when LDAP is not running.

Reviewed-By: Alexander Bokovoy <abokovoy@redhat.com>

2015-07-07 16:31:04 +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

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

Added ipaVaultPublicKey attribute.

2015-07-07 07:44:56 +00:00

tools

Improve error handling in ipa-httpd-kdcproxy

2015-07-07 16:31:04 +02:00

webui: add mangedby tab to otptoken

2015-07-07 05:51:28 +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

Import included profiles during install or upgrade

2015-06-04 08:27:33 +00:00

Makefile.am

Change group ownership of CRL publish directory

2013-07-16 12:17:40 +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.