Repository navigation
Data-driven attestation scopes + EU Business Wallet (EBW-OID, EUCC, EU PoA) data for the company users - #27
Merged
Conversation
…r the company users users.yaml gains an `attestations:` map per user, keyed by OIDC scope; a requested scope's map is released verbatim as top-level claims - the same contract the ehic scope implements by hand, since vc's apigw requests the credential type as the scope and stores the claims as the credential's document data unchanged. A new credential type is now a users.yaml block plus a scopes_supported entry, not a Go change. Shipped data: EBW-OID (WE BUILD ds001, uri:eu.ebw.oid.1), EUCC (ds004, urn:eudi:eucc:1) and EU PoA (ds007, uri:eu.eudi.eu-poa.1) for erik-010, maria-011, jan-012 and sophie-013, with every claim the rulebooks' SD-JWT schemas mark required; a test pins that. Natural persons carry none. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
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
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.
Adds an
attestations:map to each user inusers.yaml, keyed by OIDC scope. When a scope is requested, its map is released verbatim as top-level claims - the contract theehicscope already implements by hand (vc's apigw requests the credential type as the scope and stores the returned claims unchanged as the credential's document data). From now on a new credential type is ausers.yamlblock plus ascopes_supportedentry, no Go change.Shipped synthetic data for the EU Business Wallet pilot, released under scopes
ebw_oid,eucc,eu_poa(the credential type keys sirosid-dev uses):Claim names follow the VCTMs published at registry.siros.org (webuild-consortium) and every claim the rulebooks' SD-JWT schemas mark required is present;
TestShippedUsersHaveCompleteEUBusinessWalletAttestationspins that. Natural persons carry no attestations, so requesting one of these types for them fails for lack of data rather than minting an empty credential.Pairs with the sirosid-dev change that declares the three credential types (
values-base.yamlebw_oid/eucc/eu_poa, assertion-sourced) and pins the next mini-oidc release.🤖 Generated with Claude Code