It's always so funny to go hunting for a solution to a problem only to figure out at the end of a mailing list message (and thread, to which there was no response) that you are reading, in fact reading one of your old messages from the past.
Any more thoughts on all of this? Why does SSSD even need to have it's own KDC cache? Why can it not simply query the name service(s) when it needs to find a KDC? Why is the cache only containing values from an sssd.conf configuration of a given point in history? I.e. if I change my lookup_family_order from ipv4* to ipv6* the cache of IPv4 values is actually invalid/incorrect. (And what do I do to manually get this file updated once I have changed that value?) Surely that cache should always have both IPv4 and IPv6 values in it and the lookup_family_order filters on that list that is in the cache rather than using lookup_family_order's value to populate the cache with an already filtered list. I think all of this really points out why this cache is simply not a good idea and why direct lookups, when necessary are a better option. For further reference: https://github.com/SSSD/sssd/issues/3057 https://bugzilla.redhat.com/show_bug.cgi?id=1849710 Thoughts? Cheers, b. _______________________________________________ sssd-users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
