summaryrefslogtreecommitdiff
path: root/src/db/sysdb_ranges.c
AgeCommit message (Collapse)AuthorFilesLines
2013-06-28Add support for new ipaRangeType attributeSumit Bose1-0/+16
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
2013-06-09DB: Don't add invalid rangesOndrej Kos1-7/+10
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)
2013-01-15Move range objects into their own top-level tree.Simo Sorce1-9/+5
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.
2013-01-07Remove redundant definition.Simo Sorce1-1/+1
We had 2 defines for the same class. Consolidate and remove confusion.
2012-10-26sysdb: look for ranges in the parent treeSumit Bose1-1/+4
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.
2012-09-10SYSDB: NULL-terminate the output of sysdb_get_{ranges,subdomains}Jakub Hrozek1-1/+2
2012-09-04Unify usage of sysdb transactions (part 2).Michal Zidek1-4/+4
2012-06-21Add support for ID rangesSumit Bose1-0/+345