Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: credentials-plugin
-
Labels:None
-
Similar Issues:
Description
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)
Attachments
Issue Links
- is related to
-
JENKINS-44171 Editing the "description" field of a global credential deletes the "usage" history.
-
- Closed
-
-
JENKINS-41817 Credential usage is lost on rename
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue is related to |
Link |
This issue is related to |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Code changed in jenkins
User: Stephen Connolly
Path:
src/main/java/com/cloudbees/plugins/credentials/CredentialsStoreAction.java
http://jenkins-ci.org/commit/credentials-plugin/9983413e8ff390c13a14aa96a3fc35f22a3f7204
Log:
[FIXED JENKINS-43263] Mix a hash of the secret value into the fingerprint to remove false duplicate usage tracking