[Docs] Clarify provider credential fingerprint security model - #1549
Merged
mrubens merged 3 commits intoAug 23, 2026
Conversation
Contributor
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
roomote-roomote
Bot
changed the title
mrubens
marked this pull request as ready for review
August 23, 2026 12:48
mrubens
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
August 23, 2026 12:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Documented the security model around the provider credential fingerprint helper. The helper still produces the same keyed HMAC-SHA-256 value truncated to 12 hexadecimal characters.
Why this change was made
CodeQL alert #108 models provider API keys as passwords and recommends a password KDF. These fingerprints are deterministic, non-secret identifiers used for grouping and deduplication, not password verifiers, so password-hashing semantics do not apply.
Impact
There is no runtime behavior change. The documentation makes the false-positive rationale durable without obscuring data flow or weakening CodeQL analysis.