Funny, I just came here to ask the same question. I know one approach is to configure Jenkins to use the Unix user/group database for authentication, and then configure your system to use LDAP to authenticate. For example, you can use sssd if you're running CentOS/RHEL.
However, I'd prefer not to allow everyone to log into my Jenkins box. Wondering if there's another solution. On Tuesday, June 30, 2015 at 7:58:00 AM UTC-7, Raju t wrote: > > Hi Vicki, Wondering if you get any answer for your question or you found > the solution? I am also facing something similar kind of problem where i > need functionality of more than one authorization strategy. So thought of > checking with you on what solution you got. Thanks. > > On Tuesday, August 19, 2014 at 1:33:04 PM UTC-5, [email protected] wrote: >> >> Hello, >> we are using LDAP and role-based authentication for Jenkins. Sometimes we >> are experiencing LDAP connectivity problems that renders jenkins CI >> non-operational. We would like to be able to have a non LDAP authenticated >> admin user that can login at any time even when LDAP connectivity is down. >> Is it possible to combine authentication strategies? >> Thank you! >> Vicki >> > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/74b22f1b-7e8f-4194-92d3-34eda3f59c12%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
