Skip to content

Commit

Permalink
Deployed 9c0540f to main with MkDocs 1.6.0 and mike 2.1.2
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions[bot] committed Jul 30, 2024
1 parent 330e7ac commit 5fa0e29
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 7 deletions.
9 changes: 3 additions & 6 deletions main/demo/Aries-Workshop/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -2583,9 +2583,6 @@ <h3 id="lab-1-steps-to-follow">Lab 1: Steps to Follow<a class="headerlink" href=
</ol>
<p>That's it--you should be ready to start issuing and receiving verifiable credentials.</p>
<h2 id="lab-2-getting-ready-to-be-an-issuer">Lab 2: Getting Ready To Be An Issuer<a class="headerlink" href="#lab-2-getting-ready-to-be-an-issuer" title="Permanent link">&para;</a></h2>
<p>::: todo
To Do: Update lab to use this schema: H7W22uhD4ueQdGaGeiCgaM:2:student id:1.0.0
:::</p>
<p>In this lab we will use our Traction Tenant agent to create and publish an
AnonCreds Schema object (or two), and then use that Schema to create and publish
a Credential Definition. All of the AnonCreds objects will be published on the
Expand Down Expand Up @@ -2623,7 +2620,7 @@ <h3 id="lab-2-steps-to-follow">Lab 2: Steps to Follow<a class="headerlink" href=
</ol>
</li>
<li>With the schema in place, it's time to become an issuer. To do that, you have
to create a Credential Definition. Click on the “Credential” icon in the
to create a Credential Definition. Click on the “+” icon in the
“Credential Definition” column of your schema to create the Credential
Definition (CredDef) for the Schema. The “Tag” can be any value you want — it
is an issuer defined part of the identifier for the Credential Definition.
Expand Down Expand Up @@ -2676,7 +2673,7 @@ <h3 id="lab-3-steps-to-follow">Lab 3: Steps to Follow<a class="headerlink" href=
</ol>
</li>
<li>Review the Issuance Data:<ol>
<li>Back in your Traction Tenant, refresh the list to see the updates status of the issuance you just completed (should be “credential_issued” or “credential_acked”, depending on the Wallet you are using).</li>
<li>Back in your Traction Tenant, refresh the list to see the updates status of the issuance you just completed (should be “credential_issued” or “done”, depending on the Wallet you are using).</li>
<li>Expand the issuance and again to “View Raw Content.” to see the data that was exchanged between the Traction Issuer and the Wallet.</li>
</ol>
</li>
Expand Down Expand Up @@ -2716,7 +2713,7 @@ <h3 id="lab-4-steps-to-follow">Lab 4: Steps to Follow<a class="headerlink" href=
</ol>
</li>
<li>Review the Presentation Request Result:<ol>
<li>Back in your Traction Tenant, refresh the Verifications list to see the updated status of the presentation request you just completed. It should be something positive, like “presentation_received” if all went well. It may be different depending on the Wallet you are using.</li>
<li>Back in your Traction Tenant, refresh the Verifications list to see the updated status of the presentation request you just completed. It should be something positive, like “presentation_received” or “done” if all went well. It may be different depending on the Wallet you are using.</li>
<li>If you want, expand the presentation request and “View Raw Content.” to see the presentation request, and presentation data exchanged between the Traction Verifier and the Wallet.</li>
</ol>
</li>
Expand Down
2 changes: 1 addition & 1 deletion main/search/search_index.json

Large diffs are not rendered by default.

Binary file modified main/sitemap.xml.gz
Binary file not shown.

0 comments on commit 5fa0e29

Please sign in to comment.