Not sure how HTTPS is related here, but open http://yourjenkins/whoAmI after logging in (or not) as different users and compare what's shown there to your permissions config.
Note that LDAP group resolution isn't recursive, so if user1 is member of G1, and G1 is member of G2, user1 is _not_ considered a member of G2. On 16.12.2013, at 21:46, VFloyd <vanettafl...@gmail.com> wrote: > We have recently moved our Jenkins instance behind https. We want everyone > who needs to run a build to log into Jenkins...right now Anonymous can run > builds. We have set up Role Based Strategy using LDAP and although I can > create and give it Global Rights with the "build" box checked under jobs, > people in the valid groups cannot build. It's only when I return Anonymous > build rights can anyone but the admins run a build. > > Does anyone know why anonymous is over riding all other setups? > > -- > 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.
