jenkinsci / jenkinsci/ldap-plugin
[JENKINS-8569] DomainDnsZones UnknownHostException
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 51
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
Attempting to utilise this plug-in v1.17 with Hudson 1.381 on Solaris I cannot get it to authenticate with the corporate Active Directory.
It collects all the domain controllers correctly, tries each one and every time I find this error;
Root exception is javax.naming.CommunicationException: DomainDnsZones..com:389 [Root exception is java.net.UnknownHostException: DomainDnsZones..com]]
Does it need to check this? Could it merely ignore the return value as is done here;
http://forum.springsource.org/showthread.php?t=95544
They say they solved it by changing they're code thus :-
In case someone got stuck I found the solution
ldapTemplate.setIgnorePartialResultException(true) ;
or
- david
---
Originally reported by landau351, imported from: DomainDnsZones UnknownHostException
Raw content of original issue
Attempting to utilise this plug-in v1.17 with Hudson 1.381 on Solaris I cannot get it to authenticate with the corporate Active Directory.
It collects all the domain controllers correctly, tries each one and every time I find this error;
Root exception is javax.naming.CommunicationException: DomainDnsZones.<company intranet>.com:389 [Root exception is java.net.UnknownHostException: DomainDnsZones.<company intranet>.com]]
Does it need to check this? Could it merely ignore the return value as is done here;
http://forum.springsource.org/showthread.php?t=95544They say they solved it by changing they're code thus :-
In case someone got stuck I found the solution
ldapTemplate.setIgnorePartialResultException(true) ;
or
<bean id="ldapTemplate" class="org.springframework.ldap.core.LdapTemplate" >
<property name="ignorePartialResultException" value="true"></property>
<constructor-arg ref="contextSource" />
</bean>
- david
- environment:
UNIX - Solaris
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the ldap-plugin v1.17 authentication failure with Hudson 1.381 on Solaris against Active Directory, focusing on the DomainDnsZones UnknownHostException. Review how the plugin handles the reported LDAP communication error and compare it with the referenced Spring LDAP ignorePartialResultException behavior. Done means the authentication attempt handles this condition as intended and has coverage for the affected case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100