Another option is to use something like CAS, which you can point at multiple directories, and then have Jenkins use CAS. https://wiki.jenkins-ci.org/display/JENKINS/CAS+Plugin
On Wed, Feb 12, 2014 at 8:48 AM, Les Mikesell <lesmikes...@gmail.com> wrote: > On Wed, Feb 12, 2014 at 9:15 AM, Levski Weng <levskiw...@gmail.com> wrote: > > > > I'm afraid that you're right, Jenkins doesn't accept mixed user > > authentication. I choose to stick to AD because I hope someday I could > > config SSO (Single Sign On) in Jenkins and the other web systems in my > > company. I hate to remember different user names and passwords ;-) > > I think allowing authentication methods to stack would be a big plus > (like linux PAM...). Our development environment has an assortment > of test accounts and contractors that don't exist in AD so the bulk of > the users that are in AD are now forced to maintain a separate > password. > > Is there a way to set up an LDAP server that transparently merges some > extra accounts with those already in AD? > > -- > Les Mikesell > lesmikes...@gmail.com > > -- > 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 jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.