business-partner-agent
business-partner-agent copied to clipboard
hyperledger-labs
Self Issued Credentials
Feature Request: Issue credentials to myself (holder=my wallet, subject=my public did).
The BPA allows to issue Credentials to Partners once the connection is established. But there are Use Cases where I would like to issue credentials to myself.
I can Use the Wallet to "create a document" using one of my schemas (what does that actually mean? is there a self-signed VC being created in the wallet? Apparently I do not need a credential definition, so this seems to be just a BPA internal "document"?). But I can not send a presentation of such a "document" to a business partner.
Documents are currently only used as a basis to get verifications (verifiable credentials) from third parties or to be included in the public profile. In the public profile they are signed as part of the verifiable presentation, but are not represented as an AnonCred.
We would like to support the use case to send presentations based on the document to a partner or answer presentation requests with the documents. However, I'm not a fan of issuing an AnonCred to myself and that everyone needs CredDefs on the ledger for self-signed VCs.
We could support adding attributes from documents as self-attested attributes to presentations, but this does not allow to convey the information that the attribute should be understood in the context of a specific schema.
One of the next items on our roadmap is the support of issue-credential-v2 and present-proof-v2 with DIF presentation exchange and JSON-LD VCs. We'll take your feature request in account there and I think these tools will a better solution.
On a side note. You could try adding yourself as a business partner, write a cred def and request a verification from yourself.
Ahh, awesome, many thanks. I did not know that I could add myself as a business partner. This solves my use case for now. Should I close the issue? If you also want to enable self-issued credentials through a more intuitive UI path in the context of JSON-LD credentials feel free to keep it.