AD plugin doesn't use Jenkins credentials for bind dn and password

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

XMLWordPrintable

      As the summary says, the AD plugin still uses custom fields for providing the bind dn and password instead of a credentials selector. This also makes it necessary to put a variable into JCasC files instead of a credentials ID which undermines security (because that variable has to be set somewhere).

      Please fix.

            Assignee:
            Félix Belzunce Arcos
            Reporter:
            Dirk Heinrichs
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: