The limit is 64. See LDAP_MAX_CACHEABLE in the source.
Ok. Thanks!! Having both membership_filter and membership_attribute will be
increasing the load on your directory and the number of queries being sent.
I commented out the membership_attribute and corrected the membership_filter and now at first it is getting only the groups determined in a specific OU that I configured and connecting correctly on the wifi. I appreciate the help from both of you! Em seg., 22 de mai. de 2023 às 13:42, Alan DeKok <aland@deployingradius.com> escreveu:
On May 22, 2023, at 12:12 PM, dextá <dexter7bbot@gmail.com> wrote:
Is there any limit on how many groups can be cached via ldap module?
The limit is 64. See LDAP_MAX_CACHEABLE in the source.
I ask because I have some users who have 80 groups in their profile. This is because we use AD + Moodle to manage the courses.
This particular user is unable to connect to the Wi-Fi. I suspect that the reason might be having too many groups in their profile.
Perhaps also read the debug output as suggested by all o the documentation.
The debug output will show which groups matched. You can use that information to see if the group exists in LDAP, but isn't being matched in FreeRADIUS. If so, it's likely due to the LDAP_MAX_CACHEABLE flag.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html