-
Notifications
You must be signed in to change notification settings - Fork 0
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
What does your offer credential contain? #6
Comments
|
|
@brianorwhatever cool cool thanks for sharing! I see we have a lot of work on aligning where we go on this. I assume this falls back to the specific profile one follow and that DIDCom has alot of options of where it can go. Want to elaborate on what each message does so what we can get an understanding of its values :D |
Yep - keep in mind this is my planned approach, i am still working on implementation so am not set in stone on any of this. I pulled this from the WACI profile while trying to understand how credential manifest works. some adjustments for our use case as well. first attachment (
second attachment (
So - Credential Manifest looks like it still has moving pieces which are not in alignment with above. It looks like it will do what we want for this but I still need to study it a bit more. I wonder if I should drop it.. |
Note: I removed the |
Note: I updated the presentation definition to only have a challenge and no domain. I'm getting confused in PE so this will make it simpler |
Currently working on some actionsteps forward to agree: https://docs.google.com/spreadsheets/d/1ntGKxERXOAlazV8QcwcqShUG_5g0IN9jtVYPw5GTR-Y/edit?disco=AAAAiaGzyd8 But we want to do credential manifest, and that does involve multiple attachments. So to understand this better its time to freshen up the credential manifest spec |
Did we get any further with the community on alignment here? I asked in the DID com group today, a bit late, but started a bit. Aslong as we say, we want to support credential manifest, we might have to as credentila manifest group for thoughst around the exchange attachments? Who will that be? |
We have decided to drop the "fulfillment" side of the CM object in the offer message. The minimum message which still allows for DID Auth is below
|
what I implemented below
|
What we need to work out here are commonalities and where do we need to adjust according to the spec of JFF. Meaning that we find a shared JSON structure inside the attachement or where do we put the layer
The text was updated successfully, but these errors were encountered: