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

reverse-proxy-auth-plugin Advanced LDAP Configuration is showing ERROR

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • None
    • Jenkins ver. 1.651.2
      RHEL

      I have first tested the LDAP configuration using the LDAP plugin and it worked without issues.

      I have then changed the security realm to use "HTTP Header by reverse proxy" and have setup the Advanced section for LDAP using the same configuration.

      I setup Project-based Matrix Authorization Strategy.

      I am able to login using the Proxy, but if I go directly to the website and login I cannot.

      I am wondering if this is an issue or expected behavior or anyway to use both "HTTP Header by reverse proxy" and "LDAP"

      Even though I have validated the inputs and values for [Server | Manager DN | Manager Password ] - I'm seeing the following errors by inputs:

      HTTP ERROR 404

      Problem accessing /securityRealms/LDAPSecurityRealm/serverCheck. Reason:
      Problem accessing /configureSecurity/'/securityRealms/LDAPSecurityRealm/serverCheck.
      Reason:
      Not Found

      Then when I try to login via the website I get this error:
      Problem accessing /j_acegi_security_check. Reason:
      Not Found

          [JENKINS-36156] reverse-proxy-auth-plugin Advanced LDAP Configuration is showing ERROR

          John Ruperto added a comment -

          Are there any updates to this? We are having the same issue in our organization.

          John Ruperto added a comment - Are there any updates to this? We are having the same issue in our organization.

          I have seen this error with Jenkins 1.625.3 on Windows 7 with reverse proxy auth plugin 1.5, and ldap plugin 1.11.

          Terrence Dunnigan added a comment - I have seen this error with Jenkins 1.625.3 on Windows 7 with reverse proxy auth plugin 1.5, and ldap plugin 1.11.

          Jens Beyer added a comment -

          Just found this: https://groups.google.com/forum/#!topic/jenkinsci-users/HBHxN8SG2lw in the web. Someone found the causing commit in Jenkins and indeed says it is a bug in Reverse Proxy Auth Plugin.

          Jens Beyer added a comment - Just found this: https://groups.google.com/forum/#!topic/jenkinsci-users/HBHxN8SG2lw  in the web. Someone found the causing commit in Jenkins and indeed says it is a bug in Reverse Proxy Auth Plugin.

          Allan BURDAJEWICZ added a comment - - edited

          Allan BURDAJEWICZ added a comment - - edited The bogus check URLs have eventually been removed in version 1.7.4 by https://github.com/jenkinsci/reverse-proxy-auth-plugin/commit/3e4b65ef8f8d352175734e26a0ebf1b4afe19e34#diff-c27d84a9b00ca4182f5870e31ba8ea00229016b443d933056a626783389c2cb9 . The 404 are red herrings.

            Unassigned Unassigned
            jhdevci Jason Hammond
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: