On Thu, 2011-12-01 at 16:27 +0100, Jakub Hrozek wrote:Hi, As we work on the Sudo integration with Pavel, I'm thinking about how should we handle our cache. On one hand, I think our cache should be complete and possibly up to date to allow seamless offline operation. In the first prototype we have now, we just download the whole tree during every request. That's not going to scale, obviously. There can be many rules and downloading them all can get expensive. I think we can use the following mechanism: 1) the backend would schedule a periodic task to download all rules,
much like the current enumeration task. There may be an option to fine tune how often should the task start. 2) when a request comes, we would update the cache that affects the user only(*). We keep an in-memory timeout per user so that subsequent requests from the same user are handled fast. Does that sound OK? * even native sudo only searches for "(|(sudoUser=ALL)(sudoUser=username)(sudoUser=%group1)(sudoUser=%group2))" so we can limit the online update the same wayIt's interesting that native SUDO only supports lookups that way. It doesn't take into account the possibility of rules that affect the user as a member of a netgroup applying to a rule. Granted, most netgroups are used as a mechanism for restricting the *host* rather than users, but it's still a possibility that we should consider. Unless we're going to make the assumption that it's sufficient to trust netgroup membership to the enumeration task instead.
_______________________________________________ sssd-devel mailing list sssd-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/sssd-devel
-- Thank you, Dmitri Pal Sr. Engineering Manager IPA project, Red Hat Inc. ------------------------------- Looking to carve out IT costs? www.redhat.com/carveoutcosts/