You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(e2e): repair badge-disclosure gated join; prove the GitHub-badge gate
The gated-join happy path was silently broken by SDK drift: @ministryofmany/client
now pins each badge-VC key to the issuer did:web document's assertionMethod
(fetched from /.well-known/did.json, kid-scoped so the id_token key cannot
attest a badge) and binds each badge to the login via the pairwise subject DID
`did:web:<host>:u:<id_token sub>`. The e2e mock issuer still served only
/.well-known/jwks.json and minted VC subjects as `...:users:<sanitized-sub>`,
so EVERY disclosed badge landed in `rejected` (fail-closed) and no badge-gated
join could complete - the whole disclosure path was dead end to end, unnoticed
because e2e is not in CI.
Fix the mock to Minister's post-MIN-1 contract:
- serve /.well-known/did.json with the badge key in assertionMethod;
- mint the badge subject as `did:web:<host>:u:<raw id_token sub>`;
- stamp the coarse issuanceMonth claim for disclosure fidelity.
Add e2e/09: a user disclosing an oauth-account (provider=github) badge joins
the github-devs sub-forum and gets the github-dev role - the happy-path
counterpart to the spec-08 deny, exercising the full authorize-with-badge-scope
-> disclose -> verify -> gate -> membership path (task #40).
0 commit comments