sssd.git/src/db/sysdb_ranges.c, branch token3

Add support for new ipaRangeType attribute

2013-06-28T18:20:59+00:00

Recent versions of FreeIPA support a range type attribute to allow
different type of ranges for sub/trusted-domains. If the attribute is
available it will be used, if not the right value is determined with the
help of the other idrange attributes.

Fixes https://fedorahosted.org/sssd/ticket/1961

DB: Don't add invalid ranges

2013-06-09T11:58:18+00:00

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

When saving or updating ranges, skip those which are invalid (not
provided ipaNTTrustedDomainSID or ipaSecondaryBaseRID, or both provided
at the same time)

Move range objects into their own top-level tree.

2013-01-15T09:49:20+00:00

Storing ranges for multiple domains under any specific domain is
somewhat aritrary and unnecessary.
Put ranges under cn=ranges,cn=sysdb, without involving any specific
domain subtree.
This allows us to avoid using sysdb->domain in ranges functions.
Also storing other subdomains data under the parent domain tree felt
wrong, all other domain specific data is under their own subtree.
Moving this data in its own place seems a better solution.

Remove redundant definition.

2013-01-07T09:03:11+00:00

We had 2 defines for the same class.
Consolidate and remove confusion.

sysdb: look for ranges in the parent tree

2012-10-26T08:32:05+00:00

Make sure the right sub-tree in the cache is used to search for ranges.
Sub-domain trees do not have range objects only the tree of the parent
domain.

SYSDB: NULL-terminate the output of sysdb_get_{ranges,subdomains}

2012-09-10T08:32:29+00:00

Unify usage of sysdb transactions (part 2).

2012-09-04T11:56:32+00:00

Add support for ID ranges

2012-06-21T19:30:21+00:00