As Daniel said: You need a single base node to start the search.
(see
http://www.idevelopment.info/data/LDAP/LDAP_Resources/SEARCH_Setting_the_SCOPE_Parameter.shtml
)
Keep userSearchBase emtpy(!)
The filtering hsa to be done with the userSearchFilter.
Take a look at
Anybody, any ideas?
I am contemplating using TeamCity if we will be unable to get through this :(
On 11/26/15, Rama wrote:
> I tried keeping User search base (and also tried with User search
> filter as well) as blank, but that failed.
> I also tried with blank root DN,
As you have country -> users. You need to have a common root.
In your case that is dc=ca which given your root dn would be a blank entry.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving
I tried keeping User search base (and also tried with User search
filter as well) as blank, but that failed.
I also tried with blank root DN, that also failed. :(
On 11/26/15, James Nord wrote:
> As you have country -> users. You need to have a common root.
> In your case
I tried it now. Providing only OU=Users also does not work.
On 11/26/15, Daniel Beck wrote:
> How about:
>
> OU=Users
>
> On 26.11.2015, at 06:10, Ramaprakash Ganesan wrote:
>
>> I am trying to get all our organization users to login using their LDAP
>>
I am trying to get all our organization users to login using their LDAP
domain credentials to Jenkins.
With the options below, only users under 1 particular OU are able to login.
I want to provide multiple OUs to search from.
Our Active Directory structure is as below:
*ca -> America -> Users
How about:
OU=Users
On 26.11.2015, at 06:10, Ramaprakash Ganesan wrote:
> I am trying to get all our organization users to login using their LDAP
> domain credentials to Jenkins.
> With the options below, only users under 1 particular OU are able to login. I
> want to