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

CWALL-254 - FEATURE: added schemaValidation to CredentialRequestClient #149

Closed

Conversation

sksadjad
Copy link
Contributor

added schemaValidation parameter to the CredentialRequestClient(Builder). This parameter is an enum with 3 values: ALWAYS, NEVER, WHEN_PRESENT. When it's not configured in the builder (with available functions), we default to WHEN_PRESENT.

@sksadjad sksadjad changed the title feat: added schemaValidation to CredentialRequestClient CWALL-254 - FEATURE: added schemaValidation to CredentialRequestClient Sep 25, 2024
Copy link
Contributor

@nklomp nklomp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we adding schema validation options to a lib responsible for transport of credentials? The fact we are doing nothing with these options should also be a tell-tale sign.

Schema validation is credential format specific, not transport specific. So it should not live here.

The only potential option we could think about is an optional callback function registration for schema validation. When present call the callback with the received credentials in for instance an RP for OID4VP and holder for OID4VCI

@sksadjad
Copy link
Contributor Author

created the ticket https://sphereon.atlassian.net/browse/SDK-33 for supporting callback function for oid4vp and oid4vci flows

@sksadjad sksadjad closed this Sep 26, 2024
@sksadjad sksadjad deleted the feature/CWALL-254_add_schema_validation branch September 27, 2024 09:05
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

Successfully merging this pull request may close these issues.

2 participants