freeipa

0 Fork 0

Files

T

Pavel Vomacka 04da856256 WebUI: make Domain Resolution Order writable

Objectclass which defines the Domain Resolution Order is added to
the object only after modification. Therefore before modification of
object the attributelevelrights does not contain the 'domainresolutionorder'
attribute and the WebUI evaluates field as not writable.

'w_if_no_aci' flag was designed to make writable those fields
for which we don't have attributelevelrights.

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

Reviewed-By: Petr Vobornik <pvoborni@redhat.com>

2017-11-16 19:54:49 +02:00

certmonger

ipa-cacert-manage renew: switch from ext-signed CA to self-signed

2017-10-18 12:34:03 +02:00

conf

Remove XPI and JAR MIME types from httpd config

2017-11-01 12:39:19 +01:00

html

browser config: cleanup after removal of Firefox extension

2017-09-21 10:27:14 +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

Backup ipa-custodia conf and keys

2017-11-13 18:10:54 +01:00

tools

Test script for ipa-custodia

2017-11-16 08:49:34 +01:00

WebUI: make Domain Resolution Order writable

2017-11-16 19:54:49 +02:00

updates

Add indexing to improve host-find performance

2017-11-07 16:49:36 +01: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.