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

Key attestation methods #32

Closed
peppelinux opened this issue May 20, 2023 · 1 comment
Closed

Key attestation methods #32

peppelinux opened this issue May 20, 2023 · 1 comment

Comments

@peppelinux
Copy link
Member

I read here

https://github.com/vcstuff/high-assurance-profile/blob/main/draft-high-assurance-profile-oid4vc-sd-jwt-vc.md#issuer-identification-and-key-resolution-to-validate-an-issued-credential-issuer-key-resolution

that only x509 and .well-known/jwt-issuer MUST be supported

At the same time I have the "perception" that Federation has a higher level for the attestation of requirements and keys, since it brings metadata, policy and custom attestations (trust marks), and that todate we don't have clear requirements to compare x509 or .well-known/jwt-issuer more or less high.

Since this new specification is dedicated to the High profile, I think it is appropriate to do a PR to obtain the JWS trust_chain header parameter within this new profile

@Sakurann
Copy link
Contributor

closing as a duplicate of #119, since that one encompasses this one

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

2 participants