Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-8743

LDAP (verify connection) does not retry

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.0.0-m4, 3.0.0
    • Fix Version/s: None
    • Component/s: LDAP
    • Labels:
      None
    • Environment:
      Chrome MacOSX
    • Story Points:
      0.5
    • Sprint:
      Sprint 66 - Föhn

      Description

      I see no evidence currently that on NX3 LDAP configuration using Verify Connection the "retry after" and "max failed attempts" (latter I believe new for NX3) is working.
      I noticed this testing NEXUS-8655 after verifying the wait seconds before timeout field was working as I expected.
      This appears to "work" in NX2, but without "max failed attempts" it basically tries to connect forever (which is probably why the third field was added). I did not check older NX3 at this time.

      On discussion with Alin Dreghiciu, he asked if I would close NEXUS-8655 if the first field was working and open a distinct ticket on the second and third fields. This is that ticket.

      Repro steps:
      1) Setup a valid LDAP (first page) but make the port an invalid port.
      2) Click verify connection. The connection will try for the number of seconds listed in the first variable then nothing. I attempted low settings and retries to get this to fire faster (such as 10/2 and 1/5).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              jtom Joe Tom
              Last Updated By:
              Peter Roth Peter Roth
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Date of First Response:

                  tigCommentSecurity.panel-title