Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-41785

Failed connection pool setup will cause LDAP failures until app server is restarted

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: RESOLVED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 12.6, 19.0
    • Fix Version/s: 20.0 [Tentative]
    • Component/s: Login
    • Labels:
    • 19 status:
      Please Merge
    • Test Plan:
      Hide
      • Configure a Sakai server with LDAP authentication.
      • Before starting the Sakai java process, use iptables to drop all packets to the LDAP server.
      • Start the Sakai server
      • Verify that it's not possible to login / be authenticated via LDAP.
      • Clear the iptables forwarding rule
      • Verify that it's now possible to login with lookup/authentication from LDAP
      Show
      Configure a Sakai server with LDAP authentication. Before starting the Sakai java process, use iptables to drop all packets to the LDAP server. Start the Sakai server Verify that it's not possible to login / be authenticated via LDAP. Clear the iptables forwarding rule Verify that it's now possible to login with lookup/authentication from LDAP

      Description

      With the unboundid LDAP provider using connection pooling, if an LDAP server is unavailable when Sakai starts, then the connection pool is not created and LDAP auth attempts will fail until the app server is restarted, even if the LDAP server comes back online.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                smarquard Stephen Marquard
                Reporter:
                smarquard Stephen Marquard
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Git Source Code