You either know who they are, or they are anonymous. Once you know their identity then you can set their permissions. Everyone in our company even sales can identify themselves against our instance but they won't see anything unless they are in at least "jenkins-users" and to make changes they require "jenkins-power-users".
Seems pretty simple to me. On 18 November 2014 15:24, Marshall <[email protected]> wrote: > Hi all, > > I'm trying to restrict the people that can successfully *login* to a > narrow set of LDAP groups. I've tried several settings, and searched for > solutions. So far I'm coming up blank. So, here I am, looking for > assistance. > > So, given the following example setup, what would be the correct settings > to use? > > Jenkins 1.581.1 (running as a windows service) > Windows Server 2008 R2 64-bit > ad.example.edu > Limit logins only to members of the group: > ad.example.edu/DEVS/abc1/Groups/abc1_developers > > To be clear, my needs can't be answered by matrix authorization. The goal > right now is to restrict *authentication*, not authorization. > > Many thanks for your time, > Marshall > > -- > 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/d/optout. > -- 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/d/optout.
