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

Enable did:jwk resolving #2396

Merged
merged 2 commits into from
Aug 23, 2023
Merged

Enable did:jwk resolving #2396

merged 2 commits into from
Aug 23, 2023

Conversation

reinkrul
Copy link
Member

@reinkrul reinkrul commented Aug 2, 2023

No description provided.

Copy link
Member

@gerardsn gerardsn left a comment

Choose a reason for hiding this comment

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

do we need a test to check all resolvers are there? (very basic like cmd/root_test.go#Test_CreateSystem?)

@reinkrul
Copy link
Member Author

reinkrul commented Aug 3, 2023

I'm thinking more of integration-style tests, but not sure yet how

@reinkrul
Copy link
Member Author

reinkrul commented Aug 4, 2023

For did:web I wrote a simple test resolving a stubbed did:web document (see #2382). I will do the same for did:jwk after the did:web PR is merged.

End-to-end doesn't make much sense for now (at least for did:web), since we can't serve did:web from the Nuts node yet. did:jwk is mainly meant for mobile wallets, so an end-to-end test would involve mimicking one. But that part of an OpenID4VP flow, which we have yet to build.

@reinkrul reinkrul merged commit f49eb7f into master Aug 23, 2023
5 checks passed
@reinkrul reinkrul deleted the enable-didjwk branch August 23, 2023 15:21
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