-
Notifications
You must be signed in to change notification settings - Fork 88
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The consent prompt currently has mdoc-specific code deep in its bowels to figure out `displayName` and also if a requested data element exists in the credential to be presented. This makes it tricky to reuse for SD-JWT VC presentations in a clean way. Simplify all this code and introduce `ConsentField` type so the caller can just pass in which fields the consent prompt should show. Also provide credential-specific specializations - `MdocConsentField` and `VcConsentField` - so we can use the same data structures for generating credential-specific responses. Finally provide helpers to build lists of these given a credential request and modify all presentation paths to use this. Other fixes: - Use correct VCT in EuPersonalId definition and our own SD-JWT PID issuer. - Generate all claims in own SD-JWT issuer, not just strings and numbers. - Use DocumentTypeRepository in DocumentDetailsScreen for SD-JWT. - Fix age_over_21 mDL requests to use age 21 instead of 18 - Comment out creation time check as it seems flaky, added a TODO Manully tested for Credman mdoc, OpenID4VP mdoc, OpenID4VP SD-JWT, Proximity mdoc presentations. For SD-JWT tested both our own issuer and Funke. Test: Manully tested, see above. Test: ./gradlew check Test: ./gradlew connectedCheck Signed-off-by: David Zeuthen <[email protected]>
- Loading branch information
Showing
17 changed files
with
552 additions
and
419 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.