Okay.  In that case you need provide the password of account configured in
Manager DN section.

On Fri, 1 Jan 2021, 3:49 pm anilkumar panditi, <anilkumar.pand...@gmail.com>
wrote:

> Hi Mk,
> Yes i have the CN,OU details i was confused what is this Manager DN
> password, also when we click on Test it prompt for credentials which i am
> giving the LDAP admin credentials.
>
> On Friday, 1 January 2021 at 13:15:02 UTC+5:30 Mk wrote:
>
>> Manager credentials should be your domain LDAP Credentials. So it
>> requires the complete CN,OU details. To get that contact your domain
>> administrators.
>>
>> On Fri, 1 Jan 2021, 1:10 pm anilkumar panditi, <anilkuma...@gmail.com>
>> wrote:
>>
>>> Okay, can you help how to create manager credentials, also i am trying
>>> from the command (what is the user id need to give in this command)
>>>
>>> ldapsearch -x -h ad-ldap-server.com
>>>  -p 389 -D "CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com"  -b 
>>> "OU=Users,OU=Division,OU=Team,DC=domain,DC=com" "(sAMAccountName=jenkins)" 
>>> -W
>>>
>>> Thanks,
>>> Anil
>>>
>>> On Friday, 1 January 2021 at 12:33:02 UTC+5:30 Mk wrote:
>>>
>>>> Hi Anil,
>>>>
>>>> Manager and manager password need to configured to validate the test
>>>> connection.
>>>>
>>>> On Fri, 1 Jan 2021, 12:29 pm anilkumar panditi, <anilkuma...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi MK,
>>>>> i am getting ldap_bind: Invalid credentials (49)
>>>>>
>>>>> what are the credentials need to give here.
>>>>>
>>>>> Thanks,
>>>>> Anil
>>>>>
>>>>> On Saturday, 22 August 2020 at 10:00:55 UTC+5:30 Mk wrote:
>>>>>
>>>>>> Hi Jeremy, Thanks for the reply. Actually *ldapsearch* command on
>>>>>> jenkins master server terminal works. Below is the response.
>>>>>>
>>>>>> ldapsearch -x -h ad-ldap-server.com -p 389 -D
>>>>>> "CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com"  -b
>>>>>> "OU=Users,OU=Division,OU=Team,DC=domain,DC=com"
>>>>>> "(sAMAccountName=jenkins)" -W
>>>>>> Enter LDAP Password:
>>>>>> # extended LDIF
>>>>>> #
>>>>>> # LDAPv3
>>>>>> # base <OU=Users,OU=Division,OU=Team,DC=domain,DC=com> with scope
>>>>>> subtree
>>>>>> # filter: (sAMAccountName=jenkins)
>>>>>> # requesting: ALL
>>>>>> #
>>>>>>
>>>>>> # search result
>>>>>> search: 2
>>>>>> result: 0 Success
>>>>>>
>>>>>> # numResponses: 2
>>>>>> # numEntries: 1
>>>>>>
>>>>>> Since i am getting reponse so seems i have permission to query the
>>>>>> AD(LDAP) server.
>>>>>>
>>>>>> Also tried *Login name case sensitivity* & *Group name case
>>>>>> sensitivity* - Both with *Case sensitive* & *Case insensitive *but
>>>>>> still same result.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Friday, August 21, 2020 at 11:44:56 PM UTC+5:30, jeremy mordkoff
>>>>>> wrote:
>>>>>>>
>>>>>>> sounds like the user is valid but not a member of any groups. Is
>>>>>>> that possible?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thursday, August 20, 2020 at 1:28:21 PM UTC-4 Mk wrote:
>>>>>>>
>>>>>>>> Hi Team,
>>>>>>>>
>>>>>>>> I am trying to configure LDAP(AD) Authentication in our Jenkins,
>>>>>>>> Below is my configuration settings, But test LDAP connection is 
>>>>>>>> failing.
>>>>>>>>
>>>>>>>> Environment:-
>>>>>>>> Jenkins Version - 2.235.5(LTS)
>>>>>>>> LDAP Plugin - 1.24
>>>>>>>>
>>>>>>>>
>>>>>>>> Server - ldap://ad-ldap-server.com
>>>>>>>> root DN: DC=domain,DC=com
>>>>>>>> User search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>>>>>>> User search filter: sAMAccountName={0}
>>>>>>>> Group search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>>>>>>> Group search filter: (&(objectclass=group)(cn={0}))
>>>>>>>> Group membership
>>>>>>>>       Group membership filter -
>>>>>>>> (&(objectCategory=group)(member:1.2.840.113556.1.4.1941:={0}))
>>>>>>>> Manager DN: CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>>>>>>> Manager Password: password
>>>>>>>> Display Name LDAP attribute: displayname
>>>>>>>> Email Address LDAP attribute: mail
>>>>>>>>
>>>>>>>>
>>>>>>>> Error Message:-
>>>>>>>>
>>>>>>>> [image: 1.png]
>>>>>>>>
>>>>>>>> Please let me know what is missing in my configuration?. Any help
>>>>>>>> would be appreciated.
>>>>>>>>
>>>>>>> --
>>>>> 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-use...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/jenkinsci-users/ff6057a3-0c96-48d9-ae83-7c8cfe234fe9n%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/ff6057a3-0c96-48d9-ae83-7c8cfe234fe9n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>> --
>>> 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-use...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/b189583d-7246-41f2-89d3-0eef98e6c718n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/b189583d-7246-41f2-89d3-0eef98e6c718n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> 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/bb7c0c3c-cec1-4761-8603-c4f324c8c8dfn%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/bb7c0c3c-cec1-4761-8603-c4f324c8c8dfn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CA%2B4Hw5ak%3DbFCm9vfEMQoQE_03qVH6%2BDewvBg7O9Q14%2BK9iSpWg%40mail.gmail.com.

Reply via email to