Hudson LDAP authentification is Case Sensitive

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Hudson HudsoLDAP authentification is case sensitive. LDAP doesn't do case
      comparaison during login verification on LDAP side. But Hudson does. I enter
      following user in my project matrix table:

      "Arnold Pipo" (with all access: Administrator)

      When I try to connect with following id: "arnold pipo", I can connect but with
      only anonymous rights. If I cannot with "Arnold Pipo", I have the correct rights
      that I defined in my matrix. It seems that authentification is ok on LDAP side,
      but Hudson seems to compare "Arnold Pipo" and "arnold pipo" but it doesn't match
      (Case problem). So it considers him as anonymous user.

            Assignee:
            Unassigned
            Reporter:
            taillant
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: