freeipa

0 Fork 0

Files

T

Pavel Vomacka 45bd31b436 Adds whoami DS plugin in case that plugin is missing

When first installation of IPA has been done when whoami
plugin was not enabled in DS by default and then IPA was
upgraded to newer versions, then after upgrade to IPA 4.5
WebUI stops working. This is caused by new requirement on
whoami DS plugin which is used to obtain information about
logged in entity.

This fix adds the whoami plugin during update in case that the plugin
is not enabled.

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

Reviewed-By: Rob Crittenden <rcritten@redhat.com>
Reviewed-By: Tibor Dudlak <tdudlak@redhat.com>

2017-09-05 14:07:02 +02:00

certmonger

Fix external renewal for CA with non-default subject DN

2017-09-01 11:46:49 +02:00

conf

Changing cert-find to go through the proxy instead of using the port 8080

2017-06-16 08:56:53 +02:00

html

fix spelling mistake; minor rewording

2017-05-19 09:52:46 +02:00

migration

logging: do not log into the root logger

2017-07-14 15:55:59 +02:00

oddjob

wsgi, oddjob: remove needless uses of Env

2017-07-14 15:55:59 +02:00

restart_scripts

Fix Certificate renewal (with ext ca)

2017-08-30 12:58:58 +02:00

Move tmpfiles.d configuration handling back to spec file

2017-08-30 13:05:23 +02:00

tools

py3: remove Exception.message appearances

2017-08-29 12:55:25 +02:00

Fixes bug in actions creating for search facet

2017-09-01 11:43:52 +02:00

updates

Adds whoami DS plugin in case that plugin is missing

2017-09-05 14:07:02 +02:00

wsgi

logging: do not log into the root logger

2017-07-14 15:55:59 +02: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.