freeipa

0 Fork 0

Files

T

Alexander Bokovoy 725899595f Create indexes for altSecurityIdentities and ipaCertmapData attributes

During an investigation into filter optimisation in 389DS it was
discovered that two attributes of the certmap query are unindexed.
Due to the nature of LDAP filters, if any member of an OR query is
unindexed, the entire OR becomes unindexed.

This is then basically a full-table scan, which applies the filter test
to the contained members.

Fixes: https://pagure.io/freeipa/issue/7932
Fixes: https://pagure.io/freeipa/issue/7933
Reviewed-By: Florence Blanc-Renaud <flo@redhat.com>

2019-07-17 17:50:07 +03:00

certmonger

Replace PYTHONSHEBANG with valid shebang

2019-06-24 09:35:57 +02:00

custodia

Replace PYTHONSHEBANG with valid shebang

2019-06-24 09:35:57 +02:00

html

Fix javascript 'errors' found by jslint

2018-09-27 16:33:25 +02:00

migration

Use new LDAPClient constructors

2019-02-05 08:39:13 -05:00

oddjob

trust-fetch-domains: make sure we use right KDC when --server is specified

2019-06-28 13:30:59 +02:00

restart_scripts

Replace PYTHONSHEBANG with valid shebang

2019-06-24 09:35:57 +02:00

Create indexes for altSecurityIdentities and ipaCertmapData attributes

2019-07-17 17:50:07 +03:00

tools

Introduce minimal ipa-client-automount.in and ipactl.in

2019-06-28 10:53:07 +02:00

Add SMB attributes for users

2019-07-01 13:21:21 +02:00

updates

Create indexes for altSecurityIdentities and ipaCertmapData attributes

2019-07-17 17:50:07 +03:00

wsgi

Add absolute_import future imports

2018-04-20 09:43:37 +02:00

Makefile.am

Move Custodia secrets handler to scripts

2019-04-26 12:09:22 +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.