Self issued credentials

[ejossev]

It would be nice to have a way to create self-issued credentials, or sign a VCs submitted by other means.
Example may be:

• submit credential via OOB, sign it and store it in the wallet
• co-sign credential already existing in a wallet
• ...

This would allow a variety of scenarios, e.g. signing a bi- and multi-lateral contracts as VCs, documenting user decision for off-line scenarios (in connection with a kind of identity credentials), submitting a filled form as a self-signed VC to the authority etc.

With emerging EUDI/PID, this can provide a robust mechanism similar to QAES, but significantly more flexible.

See also https://www.w3.org/TR/vc-use-cases/
And

[nklomp]

The wallet is technically capable of that already. The wallet identity credential is issued/signed by a DID created during onboarding. We however need to do a few things before making this available. We are integrating xstate to create FSMs/workflows decoupling logic and ui into more loosely coupled components. Refactoring of the qr service would be part of that. Then we need to address how we are creating DIDs into something done transparently, but also have the option for more expert users. Lastly we need to finish the new contact manager integration with identities and connections. Then we can properly create the UX/UI to issue credentials from existing credentials or imported credentials, as you will want to choose which DID to use. You also want something similar for on the fly VPs, you could then share with others Sent from Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Josef Sevcik ***@***.***> Sent: Thursday, October 19, 2023 1:49:21 PM To: Sphereon-Opensource/ssi-mobile-wallet ***@***.***> Cc: Subscribed ***@***.***> Subject: [Sphereon-Opensource/ssi-mobile-wallet] Self issued credentials (Issue #167) It would be nice to have a way to create self-issued credentials, or sign a VCs submitted by other means. Example may be: * submit credential via OOB, sign it and store it in the wallet * co-sign credential already existing in a wallet * ... This would allow a variety of scenarios, e.g. signing a bi- and multi-lateral contracts as VCs, documenting user decision for off-line scenarios (in connection with a kind of identity credentials), submitting a filled form as a self-signed VC to the authority etc. With emerging EUDI/PID, this can provide a robust mechanism similar to QAES, but significantly more flexible. See also https://www.w3.org/TR/vc-use-cases/ <https://www.w3.org/TR/vc-use-cases/#issue-claim> And<https://www.w3.org/TR/vc-data-integrity/#proof-sets> — Reply to this email directly, view it on GitHub<#167>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADH4BSGVKJEU2QSLABD4LJLYAEHUDAVCNFSM6AAAAAA6HB7DK2VHI2DSMVQWIX3LMV43ASLTON2WKOZRHE2TEMBSGQZDOOA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>