Skip to content

CLIENTS: EventParticipantSecretV2Client - Redact Secret Hash On Returns - #726

Merged
cjdutoit merged 4 commits into
mainfrom
users/cjdutoit/mediumfix-eventparticipantsecretv2client-redact-secret
Jul 18, 2026
Merged

cjdutoit merged 4 commits into
mainfrom
users/cjdutoit/mediumfix-eventparticipantsecretv2client-redact-secret

Conversation

@cjdutoit

Copy link
Copy Markdown
Collaborator

Security review finding #13. The V2 participant-secret client returned the full entity — including the stored SHA-256 hash in Secret — on reads, so the hash tended to reach admin UIs and API payloads and widen the offline-cracking surface.

The client now redacts Secret to null on RetrieveAll, RetrieveById, Modify, and Remove. Add still echoes the entity (the caller already holds the plaintext it submitted; documented behaviour).

Secret verification composes over the foundation IEventParticipantSecretV2Service, not this client, so the compare is unaffected — confirmed by the secret verification unit suites and all 63 acceptance tests (submit → verify → dispatch) staying green. 3027 unit + 63 acceptance pass.

Developed test-first (redaction tests red → green). Updated the affected existing unit/acceptance client tests and the client XML docs to reflect the redacted returns.

closes #725

@github-actions github-actions Bot added the CLIENTS When creating an exposer on a library that others can use label Jul 18, 2026
@cjdutoit
cjdutoit merged commit 91b948a into main Jul 18, 2026
7 checks passed
@cjdutoit
cjdutoit deleted the users/cjdutoit/mediumfix-eventparticipantsecretv2client-redact-secret branch July 18, 2026 06:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLIENTS When creating an exposer on a library that others can use

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CLIENTS: EventParticipantSecretV2Client - Redact Secret Hash On Returns

1 participant