I spoke to soon. It worked for a short while, but now I am getting several
invalid login "Invalid login information. Please try again. "
There is still nothing in the log.
What is Jenkins doing different than ldapsearch. It should communicate with
the server on default port 389. I am using a Proxy, but both Jenkins and
Java has been configured to use this proxy.
fredag 9. oktober 2015 13.47.32 UTC+2 skrev Sverre Moe følgende:
>
> I have done nothing with the LDAP configuration, but now it works. It
> takes 30 seconds before I'm logged in.
> The only thing I have done is to add Proxy configuration to Jenkins.
>
> I have tried both samaccountname and sAMAccountName. I don't think ours
> is case sensitive.
>
> Using DOMAIN\username does not work.
>
> fredag 9. oktober 2015 13.29.46 UTC+2 skrev maciej følgende:
>>
>> Sverre Moe (2015-10-09 09:22):
>>
>> User search base: ou=users
>>
>>
>> I think it should be "CN=Users".
>>
>>
>> User search filter: samaccountname={0}
>>
>> Not sure if case matters, but we use "sAMAccountName={0}"
>>
>> Manager DN: ldapu...@arctic.company.com
>>
>>
>> This is Windows AD? If so then I think you should use "domain\user"
>> format. At least it works for me.
>>
>> Regards,
>> Nux.
>>
>>
>>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/f8b9a102-d570-427f-818a-8c1faac79476%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
