FWIW, I could never get the LDAP plugin to work against ActiveDirectory,
but the ActiveDirectory plugin works like a charm.


On Wed, Apr 2, 2014 at 10:16 AM, Terry Lacy <[email protected]> wrote:

> I'm not using the Active Directory plugin.  I'm using LDAP.
>
> Terry
>
> On Tuesday, April 1, 2014 3:44:40 PM UTC-6, Richard Bywater wrote:
>>
>> Perhaps checkout the Override Domain Controllers section on this page
>> https://wiki.jenkins-ci.org/display/JENKINS/Active+Directory+plugin
>>
>> Richard.
>>
>>
>> On Wed, Apr 2, 2014 at 10:16 AM, Terry Lacy <[email protected]> wrote:
>>
>>>
>>> I'm having intermittent issues authenticating with Jenkins.  I use LDAP
>>> with Active Directory.  My Jenkins server is on Ubuntu 12.04 Server, and AD
>>> is running on Windows 2008 R2.
>>>
>>> When authentication fails, I see this in my logs:
>>>
>>> Apr 01, 2014 2:15:04 PM hudson.security.AuthenticationProcessingFilter2
>>> onUnsuccessfulAuthentication
>>> INFO: Login attempt failed
>>> org.acegisecurity.AuthenticationServiceException: LdapCallback;null;
>>> nested exception is javax.naming.PartialResultException [Root exception
>>> is javax.naming.CommunicationException: mysubdomain.mydomain.org:389[Root 
>>> exception is
>>> java.net.NoRouteToHostException: No route to host]]; nested exception
>>> is org.acegisecurity.ldap.LdapDataAccessException: LdapCallback;null;
>>> nested exception is javax.naming
>>> .PartialResultException [Root exception is 
>>> javax.naming.CommunicationException:
>>> mysubdomain.mydomain.org:389 [Root exception is 
>>> java.net.NoRouteToHostException:
>>> No route to host]]
>>>         at org.acegisecurity.providers.ldap.LdapAuthenticationProvider.
>>> retrieveUser(LdapAuthenticationProvider.java:238)
>>>         at org.acegisecurity.providers.dao.
>>> AbstractUserDetailsAuthenticationProvider.authenticate(
>>> AbstractUserDetailsAuthenticationProvider.java:122)
>>>
>>> Notice that it says "mysubdomain.mydomain.org:389" (I changed this from
>>> my real domain/subdomain).  mysubdomain.mydomain.org doesn't exist, and
>>> that's not actually the address of my AD server.  I actually have my LDAP
>>> server configured using an IP address.  In fact, I can't find "
>>> mysubdomain.mydomain.org" when I grep my configuration, so I have no
>>> idea where it's coming from, other than I suppose you could cobble it
>>> together from the root search names.
>>>
>>> Am I mistaken in believing that it's trying to show the server name it's
>>> trying to connect to in the exception?
>>>
>>> Any ideas?
>>>
>>> Terry
>>>
>>> --
>>> 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.
>



-- 
Jeff Vincent
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent

-- 
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.

Reply via email to