Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-44787

AWS Simple AD stopped working

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • None
    • Ubuntu 14.04 Linux
      Jenkins 2.6.4 (from repository)
      Active directory plugin 2.4 (tried 2.3, and 2.2 as well)
    • active-directory-2.14

      We have been using Jenkins in AWS, with Simple AD ad the authentication source. 

      It has been working fine until 2 days ago when it stopped authenticating. 

      On investigation, we get the error message below. No environment changes have been made in the last couple of weeks. 

      Error from 'TestDomain' button in plugin global security settings: 

      Any Domain Controller is reachable

      java.net.SocketException: Socket closed
      ?? at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:118)??
      ?? at java.net.SocketOutputStream.write(SocketOutputStream.java:155)??
      ?? at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)??
      ?? at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)??
      ?? at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:426)??
      ?? at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:399)??
      ?? at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:359)??
      ?? at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:214)??
      Caused: javax.naming.CommunicationException: simple bind failed: ad.bookwana.com:389 [Root exception is java.net.SocketException: Socket closed]

       

      Any suggestions on how to resolve, or further logging I'm happy to provide. 

            fbelzunc Félix Belzunce Arcos
            brianmills Brian Mills
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: