Credentials usage tracking completely redacts secrets causing false duplicate tracking

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

XMLWordPrintable

      If you are using folder scoped credentials with the same ID and same description (only differing based on the secret) then the usage tracking will track incorrectly as the secrets are completely redacted instead of being replaced with a hash (either of the secret and the store or of just the store).

      This can also show up when the secret is updated as the tracking of usage will continue against the original secret value (though this could be considered useful too)

            Assignee:
            Stephen Connolly
            Reporter:
            Stephen Connolly
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: