freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2025-02-25 18:55:28 -06:00

Files

Tibor Dudlák 22b0ae440a Create indexes for 'serverhostname' attribute

IPA installation with large number of host entries gets timeout
when invoking ipaserver.plugins.host.get_dn() method.

Resolves: https://pagure.io/freeipa/issue/6939
Reviewed-By: Martin Basti <mbasti@redhat.com>

2017-07-04 14:40:52 +02:00

certmonger

renew agent: get rid of virtual profiles

2017-05-15 12:14:28 +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

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

Turn off OCSP check

2017-06-06 13:33:54 +02:00

Create indexes for 'serverhostname' attribute

2017-07-04 14:40:52 +02:00

tools

ipa-dns-install: remove check for local ip address

2017-06-20 11:29:41 +02:00

WebUI: add support for changing trust UPN suffixes

2017-06-14 16:55:15 +02:00

updates

Create indexes for 'serverhostname' attribute

2017-07-04 14:40:52 +02:00

wsgi

wsgi plugins: mod_wsgi expects bytes as an output

2017-06-27 16:48:21 +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.