If you want to keep some audit trail, you may consider using Proof Sets or
Proof Chains with the Credential.
If the 3rd party is providing a white label experience, I would expect the
credential to just be issued normally.
Keep in mind that issuing keys don't all need to be in 1 place, I might add
a key to the associated controller from a 3rd party controlled hardware
backed kms, that I am not in control of so that the 3rd party can issue
credentials on my behalf.
OS
On Mon, Mar 23, 2020 at 8:48 AM Dmitri Zagidulin <dzagidulin@gmail.com>
wrote:
> Hi Anil,
>
> That's an interesting use case! Can you say more - what do you mean by "passed
> the issuance of credentials to a 3rd party"?
>
> On Mon, Mar 23, 2020 at 9:10 AM Anil Lewis <anillewi@ca.ibm.com> wrote:
>
>> Team,
>> How do we model verifiable credentials if the original issuer has passed
>> the issuance of credentials to a 3rd party. In the specs, I see id and name
>> but nothing more than yet. In this case, we do not have access to the 3rd
>> party keys. I do see an evidence property but not sure what should be the
>> value of the verifier property in the evidence object. Should this point to
>> the original issuer's website?
>>
>>
>>
>> ------------------------------
>>
>> *Anil Lewis *
>> Senior Managing Consultant
>>
>>
>>
>> Mobile: 1-416-433-7015
>> Phone: 1-416-478-4681
>> E-mail: anillewi@ca.ibm.com
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
--
*ORIE STEELE*
Chief Technical Officer
www.transmute.industries
<https://www.transmute.industries>
