Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Misunderstanding of what AuthorizedNamespaces is #462

Open
davidz25 opened this issue Feb 19, 2025 · 0 comments
Open

Misunderstanding of what AuthorizedNamespaces is #462

davidz25 opened this issue Feb 19, 2025 · 0 comments

Comments

@davidz25
Copy link

davidz25 commented Feb 19, 2025

Section A.2.4. Credential Response says the following

The value of the credential claim in the Credential Response MUST be a string
that is the base64url-encoded representation of the CBOR-encoded IssuerSigned
structure, as defined in [ISO.18013-5]. This structure SHOULD contain all
Namespaces and IssuerSignedItems that are included in the AuthorizedNamespaces
of the MobileSecurityObject.

According to 18013-5 AuthorizedNamespaces is a mechanism for the issuer to convey that DeviceKey is authorized to sign data elements in that name space and to be returned in DeviceSigned. So it doesn't make any sense to say "This structure SHOULD contain all Namespaces and IssuerSignedItems that are included in the AuthorizedNamespaces of the MobileSecurityObject.". (Also, if you look at MSOs being minted today across e.g. US mDL issuers, no-one is actually using DeviceSigned at all to return data elements, as far as I know.)

I also don't think it make sense to specify what the structure SHOULD contain, I mean, it's already completely specified by 18013-5 what it contains. I would just strike the entire last sentence in the quoted paragraph.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant