summaryrefslogtreecommitdiffstats
path: root/src/db/sysdb_ranges.c
Commit message (Collapse)AuthorAgeFilesLines
* DB: Don't add invalid rangesOndrej Kos2013-06-091-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)
* Move range objects into their own top-level tree.Simo Sorce2013-01-151-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.
* Remove redundant definition.Simo Sorce2013-01-071-1/+1
| | | | | We had 2 defines for the same class. Consolidate and remove confusion.
* sysdb: look for ranges in the parent treeSumit Bose2012-10-261-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.
* SYSDB: NULL-terminate the output of sysdb_get_{ranges,subdomains}Jakub Hrozek2012-09-101-1/+2
|
* Unify usage of sysdb transactions (part 2).Michal Zidek2012-09-041-4/+4
|
* Add support for ID rangesSumit Bose2012-06-211-0/+345
generated by cgit (git 2.34.1) at 2024-05-30 23:58:50 +0000