On Thursday, February 13, 2014 12:53:08 AM UTC+8, Larry Shatzer, Jr. wrote: > > 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 >
That's EXACTLY what I want. Thank you, Larry Shatzer, Jr. > > On Wed, Feb 12, 2014 at 8:48 AM, Les Mikesell <[email protected]<javascript:> > > wrote: > >> On Wed, Feb 12, 2014 at 9:15 AM, Levski Weng >> <[email protected]<javascript:>> >> 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 >> [email protected] <javascript:> >> >> -- >> 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] <javascript:>. >> 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
