LDAP cresentials with sAMAccountName including uppercase letter does not work with Global Security

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

XMLWordPrintable

      With LDAP auth, the sAMAccountName containing uppercase case letters does not work with Global Security. For example, user ID "testuser" can be specified in the Global Security as expected. However, user ID "TEstuser" does not work as expected with the Global Security specified as TEstuser. In the Jenkis home dir there is a dir for either users/testuser/config.xml and users/TEstuser/config.xml. It just doesn't work with the ID containing uppercase letters.

        1. ldap-advanced-settings.png
          64 kB
          Stephen Connolly
        2. ldap-advanced-settings-case-expanded.png
          78 kB
          Stephen Connolly

            Assignee:
            Kohsuke Kawaguchi
            Reporter:
            Fory Horio
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: