Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-5795

ldap connection pool not created when using ssl (ldaps)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: jboss-fuse-6.2.1
    • Fix Version/s: jboss-fuse-6.3
    • Component/s: Fuse Distribution, Karaf, Security
    • Labels:
      None
    • Environment:

      fuse 6.2.1-090 and 6.2.1-107
      oracle jdk 1.8
      389 Directory Server and Active Directory
      fabric and standalone configuration

    • Steps to Reproduce:
      Hide

      1. Add params for logging to bin/setenv:
      export EXTRA_JAVA_OPTS="-Dcom.sun.jndi.ldap.connect.pool.debug=all -Dcom.sun.jndi.ldap.LdapPoolManager.debug=true"
      2. Start fuse (bin/fuse)
      3. Copy ldap-module.xml to deploy directory
      4. Note ldap-pool.txt console output on login (bin/client) and established connections to port 389 via netstat
      5. Modify params for logging and ssl enablement to bin/setenv:
      export EXTRA_JAVA_OPTS="-Dcom.sun.jndi.ldap.connect.pool.debug=all -Dcom.sun.jndi.ldap.LdapPoolManager.debug=true -Dcom.sun.jndi.ldap.connect.pool.protocol=ssl"
      6. Restart fuse
      7. Modify ldap-module.xml for ldaps
      8. Note ldaps-pool.txt console output on login (bin/client) and lack of established connections to port 636 via netstat

      Show
      1. Add params for logging to bin/setenv: export EXTRA_JAVA_OPTS="-Dcom.sun.jndi.ldap.connect.pool.debug=all -Dcom.sun.jndi.ldap.LdapPoolManager.debug=true" 2. Start fuse (bin/fuse) 3. Copy ldap-module.xml to deploy directory 4. Note ldap-pool.txt console output on login (bin/client) and established connections to port 389 via netstat 5. Modify params for logging and ssl enablement to bin/setenv: export EXTRA_JAVA_OPTS="-Dcom.sun.jndi.ldap.connect.pool.debug=all -Dcom.sun.jndi.ldap.LdapPoolManager.debug=true -Dcom.sun.jndi.ldap.connect.pool.protocol=ssl" 6. Restart fuse 7. Modify ldap-module.xml for ldaps 8. Note ldaps-pool.txt console output on login (bin/client) and lack of established connections to port 636 via netstat
    • Sprint:
      Sprint 6 - towards CR1

      Description

      Connection pools are not established when using ldaps, even though they are configured via ldap-module.xml or a fabric profile. Authentication succeeds in both cases, the pool configuration does not succeed for ldaps.

        Gliffy Diagrams

          Attachments

          1. ldap-module.xml
            1 kB
          2. ldap-pool.txt
            5 kB
          3. ldaps-pool.txt
            0.5 kB

            Issue Links

            is related to

            KARAF-4607 Loading...

              Activity

                People

                • Assignee:
                  grgrzybek Grzegorz Grzybek
                  Reporter:
                  rhn-support-shiggs Stephen Higgs
                  Tester:
                  Josef Ludvicek
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: