sssd.git/src/tests/cwrap, branch dpstr

TESTS: Check return value of check_leaks_pop

2015-11-11T11:10:45+00:00

Reviewed-by: Petr Cech

TESTS: Initialize leak check

2015-11-11T11:10:43+00:00

If leak_check_setup is not called then global_talloc_context
was not initialized and check_leaks_pop(global_talloc_context) will fail.

Reviewed-by: Petr Cech

BUILD: Remove SSS_CRYPTO_LIBS from common libraries

2015-10-26T06:23:15+00:00

The similarcahnge was done in main makefile by change
69b46c32357ccf1aab9c0bd6d1afa33a8724ad77

Reviewed-by: Jakub Hrozek

BUILD: Remove unused variables

2015-10-26T06:23:11+00:00

LIBCAPNG_{CFLAGS,LIBS} are not defined anywhere in sssd.
It could be introduced as copy&paste error from different project.

Reviewed-by: Jakub Hrozek

responder_common_tests: Removed unused libraries

2015-10-26T06:23:07+00:00

responder_common_tests does not use any function which requires to link
with UNICODE linraries or with libsss_crypt

Reviewed-by: Jakub Hrozek

sysdb: add sysdb_search_user_by_cert() and sysdb_search_object_by_cert()

2015-06-19T16:48:13+00:00

Related to https://fedorahosted.org/sssd/ticket/2596

Reviewed-by: Pavel Březina

CONFIG: Add SSS_STATEDIR as VARDIR/lib/sss

2015-06-16T16:27:19+00:00

Reviewed-by: Michal Židek

sdap: properly handle binary objectGuid attribute

2015-03-20T11:26:47+00:00

Although in the initial processing SSSD treats the binary value right at
some point it mainly assumes that it is a string. Depending on the value
this might end up with the correct binary value stored in the cache but
in most cases there will be only a broken entry in the cache.

This patch converts the binary value into a string representation which
is described in [MS-DTYP] and stores the result in the cache.

Resolves https://fedorahosted.org/sssd/ticket/2588

Reviewed-by: Jakub Hrozek

tests: convert all unit tests to cmocka 1.0 or later

2015-03-11T13:39:35+00:00

All tests now use the cmocka-1.0-compatible API.

Reviewed-by: Lukáš Slebodník

server-tests: use strtouint32 instead strtol

2015-01-15T09:31:46+00:00

PID may be greater than 0xffff thus we remove this check but it is
supposed to be in range of uint32.

There are also some improvements to get more information from
assertions.

Reviewed-by: Lukáš Slebodník