Karl P created JENKINS-13894:
--------------------------------
Summary: active-directory: cannot login if server has invalid
time/network connection
Key: JENKINS-13894
URL: https://issues.jenkins-ci.org/browse/JENKINS-13894
Project: Jenkins
Issue Type: Bug
Components: active-directory
Environment: jenkins 1.427
Reporter: Karl P
Priority: Minor
Jenkins is running on a windows machine, with active directory in use for user
authentication. This normally all works fine. For some reason, the host
started having errors, which prevented remote logins even [1] While this was
happening, jenkins kept working, but you could not login. Attempts to login
through a 500 with the following stack trace:
{code}
com4j.ComException: 80040e37 (Unknown error) : An operations error occurred.
: .\invoke.cpp:460
at com4j.Wrapper.invoke(Wrapper.java:122)
at $Proxy32.execute(Unknown Source)
at
hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.getDnOfUserOrGroup(ActiveDirectoryAuthenticationProvider.java:117)
at
hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:73)
at
org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:119)
at
org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:195)
at
org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:45)
at
org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:71)
at
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:61)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
at
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at
winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:244)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150)
at java.lang.Thread.run(Unknown Source)
Caused by: com4j.ComException: 80040e37 (Unknown error) : An operations error
occurred.
: .\invoke.cpp:460
at com4j.Native.invoke(Native Method)
at com4j.StandardComMethod.invoke(StandardComMethod.java:95)
at com4j.Wrapper$InvocationThunk.call(Wrapper.java:258)
at com4j.Task.invoke(Task.java:44)
at com4j.ComThread.run0(ComThread.java:149)
at com4j.ComThread.run(ComThread.java:125)
{code}
When the machine was "fixed" and remote desktop connections worked again,
logins to jenkins also worked again. This is a very minor issue, but just
something that could be improved :) It should report something humanly usable,
not a 500 page. For what it's worth, and it isn't much, remote desktop
connections were refused with the following error message (Which I'd never seen
before):
"Remote Desktop cannot verify the identity of the remote computer because there
is a time or date difference between your computer and the remote computer.
Make sure your computer's clock is set to the correct time, and then try
connecting again. If the problem persists, please consult your doctor" (well,
not the doctor part)
Disabling all security settings possible didn't help, this required a trip to
the server room! I know 1.427 isn't the latest version, but I don't see
anything in the changelog to suggest that this has been fixed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
