aa8608253630d8f3679dba5771ed019051c96930 |
|
13-Dec-2017 |
Fabiano Fidêncio <fidencio@redhat.com> |
CACHE_REQ: Fix typo: cache_reg -> cache_req
Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com>
Reviewed-by: Jakub Hrozek <jhrozek@redhat.com> |
2af80640f18966d65cf82106059ce3c060df93bf |
|
11-Dec-2017 |
amitkuma <amitkuma@redhat.com> |
cache: Check for max_id/min_id in cache_req
The cache_req code doesn't check the min_id/max_id
boundaries for requests by ID.
Extending the .lookup_fn function in each plugin
that searches by ID for a check that returns non-zero
if the entry is out of the range and 0 if not.
Resolves: https://pagure.io/SSSD/sssd/issue/3569
Reviewed-by: Jakub Hrozek <jhrozek@redhat.com>
Reviewed-by: Fabiano Fidêncio <fidencio@redhat.com> |
a6eb9c4c3ff68d134bc745e8374f182737e9696b |
|
06-Dec-2017 |
Jakub Hrozek <jhrozek@redhat.com> |
CACHE_REQ: Implement the plugin methods that utilize the domain locator API
Mainly, this patch adds handlers for the dp_get_domain_check_fn(),
dp_get_domain_send_fn() and dp_get_domain_recv_fn() functions to
requests that resolve objects by ID.
This patch also adds domain-local negcache setter for by-id methods
Previously, the by-ID methods only used global negative cache setters
because the ID space is global and we always iterated over all domains.
However, with addition of the domain locator plugin, we want also
to skip only certain domains and the easiest way to to so is to add
the IDs for domains that do not contain these IDs to the negative cache
with the get-account-domain request.
Therefore this patch also adds per-domain negative cache setters for
the three plugins that search by ID.
Reviewed-by: Pavel Březina <pbrezina@redhat.com>
Reviewed-by: Sumit Bose <sbose@redhat.com> |
0e238c259c066cf997aaa940d33d6bda96c15925 |
|
27-Nov-2017 |
Sumit Bose <sbose@redhat.com> |
sysdb: do not use objectClass for users and groups
The majority of the object in the SSSD cache are users and groups. If
there are many user and groups in the cache the index objects of the
objectclass attributes 'user' and 'group' become large because the
must hold references to all objects of those object classes.
As a result the management of these index objects becomes costly because
they must be parsed and split apart quite often. Additionally they are
mostly useless because user and groups are lookup up by more specific
attributes in general.
Only when enumerating all user or groups this kind of index might be
useful.
There are two way of removing this kind of index from the user and group
objects. Either by removing objectClass from the list of indexes and add
a new attribute to all other type of object we want and index for. Or by
replacing objectClass with a different attribute for the user and group
objects. After some testing I think the latter one is the more reliable
one and implemented it in this patch.
Related to https://pagure.io/SSSD/sssd/issue/3503
Reviewed-by: Fabiano Fidêncio <fidencio@redhat.com>
Reviewed-by: Jakub Hrozek <jhrozek@redhat.com> |
4df7aec645f87342f3a5146062abcb15f71f4fd9 |
|
08-Feb-2017 |
Pavel Březina <pbrezina@redhat.com> |
cache_req: move dp request to plugin
This will allow to use cache req even for object that do not use
account request such as hosts.
Reviewed-by: Jakub Hrozek <jhrozek@redhat.com> |
7a2ca8d776df685bddbb64370181fb32d776f676 |
|
19-Dec-2016 |
Pavel Březina <pbrezina@redhat.com> |
cache_req: return well known objects in object by sid
Resolves:
https://fedorahosted.org/sssd/ticket/3151
Reviewed-by: Lukáš Slebodník <lslebodn@redhat.com> |