57c5ea8825c7179fd93382dbcbb07e828e5aec19 |
|
29-Jan-2018 |
René Genz <liebundartig@freenet.de> |
Fix minor spelling mistakes in tests/cmocka/*
Reviewed-by: Lukáš Slebodník <lslebodn@redhat.com> |
afadeb1a530ff010a2f9a7552562576b843c874b |
|
03-Mar-2017 |
Jakub Hrozek <jhrozek@redhat.com> |
SYSDB: When searching for UPNs, search either the whole DB or only the given domain
The search-by-UPN functions always searched for the whole domain. In
some cases, the caller depends on the result coming from the domain
specified by the 'domain' parameter. This is the case in the cache_req
code at least. Even though it should be safe to just switch to always
searching the whole domain, in order to allow us to examine the code
carefully and test each codepath, let's introduce a boolean option to
the search functions. Currently it defaults to false in all codepaths
and as we test the individual ones, we can flip the option to true until
we finally remove the option altogether.
Reviewed-by: Sumit Bose <sbose@redhat.com> |
f1e3364a72eb75673d10cf8c97ba8f1d7a385405 |
|
08-Feb-2017 |
Petr Čech <pcech@redhat.com> |
TEST: create_multidom_test_ctx() extending
Function create_multidom_test_ctx() prepares test environment for
multidomains. This patch enables setting of different params for
each domain.
Resolves:
https://fedorahosted.org/sssd/ticket/3230
Reviewed-by: Jakub Hrozek <jhrozek@redhat.com>
Reviewed-by: Sumit Bose <sbose@redhat.com> |
00f3c5cd03625357e226552084e499965512bf53 |
|
10-Aug-2016 |
Lukas Slebodnik <lslebodn@redhat.com> |
SYSDB: Avoid optimisation with modifyTimestamp for users
The usage of modifyTimestamp needn't be a reliable way
for detecting of changes in user entry in LDAP.
The authorisation need to rely current data from LDAP
and therefore we will temporary disable optimisation with
modifyTimestamp and we will rather rely on deep comparison
of attributes. In he future, it might be changed and
responders might control the optimization level.
Resolves:
https://fedorahosted.org/sssd/ticket/3110
Reviewed-by: Jakub Hrozek <jhrozek@redhat.com> |
eb92441b65e0db9e64c88a57eb74358640e85d56 |
|
05-Aug-2016 |
Jakub Hrozek <jhrozek@redhat.com> |
SYSDB: Fix setting dataExpireTimestamp if sysdb is supposed to set the current time
sysdb is already able to retrieve the current timestamp if the caller
doesn't specify it. However, for the timestamp cache this came too late
and the timestamp cache used zero as the 'now' time.
Resolves:
https://fedorahosted.org/sssd/ticket/3064
Reviewed-by: Pavel Březina <pbrezina@redhat.com> |
5d0d0f8067fb53285a38fe978cfa36dbeb53be9b |
|
06-Jul-2016 |
Lukas Slebodnik <lslebodn@redhat.com> |
sysdb: Use ldb_result as output in sysdb_search_ts_{users,groups}
Passing address of unsigned to the output argument size_t causes
access out of boundaries for type unsigned and and wrong data
on big endian. It looks like functions sysdb_search_ts_{users,groups}
need to store results in structure ldb_result anyway for further processing.
Therefore it will be better to convert output arguments
size_t* + ldb_message*** into structure ldb_result and avoid using
additional helper variable with type size_t before each invocation
of these functions.
Reviewed-by: Sumit Bose <sbose@redhat.com> |
c7c1941f9045531044121520fc2ca0e048732c25 |
|
06-Jul-2016 |
Lukas Slebodnik <lslebodn@redhat.com> |
test_sysdb_ts_cache: Do not use wrong pointer for output argument
The function sysdb_search_groups expects pointer to size_t as an output
argument msgs_count. However, struct ldb_result has type unsigned for element
count. The size of unsigned is lower then size of size_t on some platforms.
Therefore we should not cast to pointer to size_t if we want to write
count of messages into struct ldb_result -> count.
The valgrind did not detect write out of boundary for the element count
because it is the 1st element in structure ldb_result. It didn't cause any
problem on little endian because the most significant part of size_t was
properly stored to type unsigned.
We firstly store to output argument _msgs_count and then to output argument
_msgs in the function sysdb_cache_search_entry therefore element msgs was not
damaged and contained correct data.
Reviewed-by: Sumit Bose <sbose@redhat.com> |
d36f4db9bb5efc63b94190cca25adb08ee56971c |
|
23-Jun-2016 |
Jakub Hrozek <jhrozek@redhat.com> |
TESTS: Add a unit test for timestamps caches
Reviewed-by: Sumit Bose <sbose@redhat.com> |