sssd.git/src/providers/dp_backend.h, branch simo

DP: invalidate all cached maps if a request for auto.master comes in

2012-12-18T16:25:34+00:00

If the Data Provider receives a request for the auto.master map, it
passes on a flag to let the actual provider let know he should
invalidate the existing maps

FO: Check server validity before setting status

2012-09-13T14:51:38+00:00

The list of resolved servers is allocated on the back end context and
kept in the fo_service structure. However, a single request often
resolves a server and keeps a pointer until the end of a request and
only then gives feedback about the server based on the request result.

This presents a big race condition in case the SRV resolution is used.
When there are requests coming in in parallel, it is possible that an
incoming request will invalidate a server until another request that
holds a pointer to the original server is able to give a feedback.

This patch simply checks if a server is in the list of servers
maintained by a service before reading its status.

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

Duplicate detection in fail over did not work.

2012-08-15T11:51:22+00:00

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

Change refreshing of subdomains

2012-08-01T20:24:44+00:00

This patch keeps a local copy of the subdomains in the ipa subdomains plugin
context.
This has 2 advantages:
1. allows to check if anything changed w/o always hitting the sysdb.
2. later will allows us to dump this information w/o having to retrieve it
again. The timestamp also allows to avoid refreshing too often.

Use a more tractable name for subdomain request

2012-08-01T20:24:44+00:00

I am all for readable names, but there is a tradeof between expressing purpose
and compactness.

Change subdomain_info

2012-08-01T20:24:43+00:00

Rename the structure to use a standard name prefix so it is properly
name-spaced, in preparation for changing the structure itself.

Primary server support: basic support in failover code

2012-08-01T14:19:41+00:00

Now there are two list of servers for each service. If currently
selected server is only backup, then an event will be scheduled which
tries to get connection to one of primary servers and if it succeeds,
it starts using this server instead of the one which is currently
connected to.

Primary server support: introduce concept of reconnection

2012-08-01T14:19:41+00:00

This patch adds two support functions for adding reconnection callbacks
and invoking such callbacks. The concept of reconnection is simple: stop
using current connection for for new queries to the server without
actually going offline.

Remove unused member of be_req

2012-07-27T08:46:46+00:00

Move SELinux processing from session to account PAM stack

2012-07-27T08:37:06+00:00

The idea is to rename session provider to selinux provider. Processing
of SELinux rules has to be performed in account stack in order to ensure
that pam_selinux (which is the first module in PAM session stack) will
get the correct input from SSSD.

Processing of account PAM stack is bound to access provider. That means
we need to have two providers executed when SSS_PAM_ACCT_MGMT message
is received from PAM responder. Change in data_provider_be.c ensures
just that - after access provider finishes its actions, the control is
given to selinux provider and only after this provider finishes is the
result returned to PAM responder.