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

allow local issuance for did:web #2641

Closed
wants to merge 1 commit into from

Conversation

woutslakhorst
Copy link
Member

closes #2640

this allows an issuer to issue to a wallet within the same node. This only happend when the VC is not public, not published, the receiver is a did:web and when it's owned by the node.

Copy link
Member

@reinkrul reinkrul left a comment

Choose a reason for hiding this comment

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

I don't like this monkey patch too much. The wallet owner now hasn't anything to decide whether it actually wants the credential. And it's a bit of magic with obscure limitations (no JWT).

Wouldn't it be better to provide a REST API to load credentials into the wallet? Then the existing issue API (no publish) can be used to create the VC, then the new API (something like POST internal/vcr/v1/holder/{did}/vc for putting it in any wallet.

return createdVC, nil
}

func (i issuer) tryLocalIssuance(ctx context.Context, options CredentialOptions, createdVC *vc.VerifiableCredential) {
if options.Publish {
// not supported, return silently
Copy link
Member

Choose a reason for hiding this comment

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

but JWTs can't be loaded into the local wallet this way?

@woutslakhorst
Copy link
Member Author

I don't like this monkey patch too much. The wallet owner now hasn't anything to decide whether it actually wants the credential. And it's a bit of magic with obscure limitations (no JWT).

Wouldn't it be better to provide a REST API to load credentials into the wallet? Then the existing issue API (no publish) can be used to create the VC, then the new API (something like POST internal/vcr/v1/holder/{did}/vc for putting it in any wallet.

That would be a nice intermediate solution. It would require 2 API calls for vendors to create their credentials. It would help us to continue building the rest.

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.

support self issuance for wallets
2 participants