...

Reminders: Please record the session

Targets:

1. RFC 0036Scenario: Issue a credential with the Issuer beginning with an offerGiven "2" agents
   | name | role |
   | Acme | issuer |
   | Bob | holder |
   And "Acme" and "Bob" have an existing connection
   When "Acme" offers a credential
   And "Bob" requests the credential
   And "Acme" issues the credential
   And "Bob" acknowledges the credential issue
   Then "Bob" has the credential issued​
   RFC0037

   Scenario Outline: Present Proof where the prover does not propose a presentation of the proof and is acknowledged
   Given "2" agents 
   | name | role | 
   | Faber | verifier | 
   | Bob | prover | 
   And "Faber" and "Bob" have an existing connection
   And "Bob" has an issued credential from <issuer>
   When "Faber" sends a request for proof presentation to "Bob"
   And "Bob" makes the presentation of the proof
   And "Faber" acknowledges the proof
   Then "Bob" has the proof verified

   RFC0160
   Scenario Outline: establish a connection between two agents
   Given we have "2" agents
   | name | role |
   | Acme | inviter |
   | Bob | invitee |
   When "Acme" generates a connection invitation
   And "Bob" receives the connection invitation
   And "Bob" sends a connection request to "Acme"
   And "Acme" receives the connection request
   And "Acme" sends a connection response to "Bob"
   And "Bob" receives the connection response
   And "Acme" sends <message> to "Bob"
   Then "Acme" and "Bob" have a connection
   RFC0183
   Scenario Outline: Credential revoked by Issuer and Holder attempts to prove with a prover that doesn't care if it was revoked
   Given "2" agents
   | name | role |
   | Bob | prover |
   | Faber | verifier |
   And "Faber" and "Bob" have an existing connection
   And "Bob" has an issued credential from <issuer> with <credential_data>
   When <issuer> revokes the credential
   And "Faber" sends a <request_for_proof> presentation to "Bob"
   And "Bob" makes the <presentation> of the proof
   And "Faber" acknowledges the proof
   Then "Bob" has the proof verified434, 023: Connect using OOB (invitation only) OR connect using OOB (OOB as handshake protocol)
2. OOB Reuse: Connect again using OOB (test connection reuse)
3. RFC 048: Send trust ping (both directions if possible)
4. RFC 557: Request "discover features" using one agent and send disclosure from other agent. Reverse roles if possible.

Bonus:

5. RFC 455: Test credential issuance--offer a credential using issuance v. 2 from one agent to the other. Reverse roles if applicable.
6. RFC 454: Request credential presentation from an agent holding a known credential (probably what was just issued in step 5). Reverse roles if applicable.
7. RFC 183: Revoke the credential from step 5. Reverse roles if possible.

SESSION 1:

***ASK TO RECORD SESSION***

Host: 

Scribe:

Who participated?

• Name of Participants:
• Company

What did you test?

• Targets:
• 557 Discover Features
• 048 Trust Ping
• 434 OOB
• 023 DID Exchange
• OOB Reuse
• Bonus Targets:
• 455 Issue
• 454 Present
• 183 Revocation Notification

• Other:
  
  

Successes?

Issues Identified? 

SESSION 2:

***ASK TO RECORD SESSION***

Host: 

Scribe:

Who participated?

• Name of Participants:
• Company

What did you test?

• Targets:
• 557 Discover Features
• 048 Trust Ping
• 434 OOB
• 023 DID Exchange
• OOB Reuse
• Bonus Targets:
• 455 Issue
• 454 Present
• 183 Revocation Notification

• Other:
  
  

Successes?

Issues Identified?