sssd.git/src/providers/ldap/sdap_sudo.c, branch simo

Add domain arguments to sysdb sudo functions

2013-01-11T15:43:14+00:00

sudo smart refresh: fix debug message

2013-01-07T20:47:24+00:00

sudo smart refresh: do not include usn in filter if no valid usn is known

2013-01-07T20:47:24+00:00

https://fedorahosted.org/sssd/ticket/1736

When there are no rules during first refresh, we don't have valid
USN value. We use 0 in this case, but it turned out that OpenLDAP
takes it as invalid time format (if modifyTimestamp is used instead
of USN) and thus returns no records.

Now we don't include USN/modifyTimestamp attribute in the filter
if such situasion occurs.

LDAP: initialize refresh function handler

2013-01-04T15:34:23+00:00

Add default section to switch statement

2012-12-19T17:42:58+00:00

switch statements should always have a default section. In this
particular case gcc gave a "'send_fn' may be used uninitialized in this
function" warning.

sudo: do full refresh when data provider is back online

2012-12-18T16:15:22+00:00

https://fedorahosted.org/sssd/ticket/1689

Add a online callback if the first full refresh fails due to the
provider beeing offline so we can perform the refresh as soon as
possible.

sudo: schedule another full refresh in short interval if the first fails

2012-12-18T16:15:22+00:00

https://fedorahosted.org/sssd/ticket/1689

If the first full refresh of sudo rules fails because the data provider
is offline, we will schedule another one in 2, 4, ... minutes.

check dp error in sdap_sudo_full_refresh_done()

2012-12-18T16:15:22+00:00

https://fedorahosted.org/sssd/ticket/1689

add sdap_sudo_schedule_refresh()

2012-12-18T16:15:22+00:00

Reduces amount of code duplication.

sudo: don't get stuck in rules and smart refresh when offline

2012-12-11T15:10:32+00:00

https://fedorahosted.org/sssd/ticket/1682

The problem was in following code:
if (ret != EOK || state->dp_error != DP_ERR_OK || state->error != EOK) {
    tevent_req_error(req, ret);
    return;
}

In situation when data provider error occurs (e.g. when offline),
ret == EOK but dp_error != DP_ERR_OK and we take the true branch.
This results in calling tevent_req_error(req, EOK).

Unfortunately, with EOK tevent_req_error only returns false, but
does not trigger callback and this tevent request hangs forever,
because no tevent_req_done(req) is called.