I don't think there's a need to do so. It still works without any configuration in a lot of cases. And configuration of the LDAP plugin can be annoying if you know nothing about LDAP.
I've experienced a severe issue with AD a while back (essentially JENKINS-16429; restarting Jenkins twice a week for months when several important jobs have build times of 10+ hours isn't fun), and was able to resolve them by switching to LDAP. Given the AD specific stack trace, I suggested Andrew tries this as well. On 22.02.2014, at 16:07, Baptiste Mathus <[email protected]> wrote: > Curious, would that plugin somehow be deprecated? We've been using it for > many years (since the time when Jenkins had another name that extinguished > today) without any issue. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
