Jamf Connect appears to run ldapsearch with a hardcoded nettimeout=1, which is causing delays or failures when trying to update the menu bar with user state after a successful Kerberos authentication. I’ve attempted to increase the timeout by setting NETWORK_TIME 60 in the /etc/openldap/ldap.conf file, but Jamf continues to use the same nettimeout=1 argument, ignoring the config file. Has anyone found a way to override this default or increase the timeout value used by Jamf Connect during the LDAP query?
Page 1 / 1
@tim75
I've had the same issues and concerns as you. I spoke to Jamf Support and there is no way to modify that at the moment. I submitted a feature request (Kerberos Integration - Add Preferences to specify | Jamf Nation Ideas) to the development team so that they can expose the nettimeout as a configurable variable within the menu bar configuration profile. If that is something you'd be interested in, please take a look at my post linked above and vote.
Thanks
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.