Skip to content
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

Proof Request 'Card' Not Rendering When Issued With No Restrictions #2324

Open
al-rosenthal opened this issue Dec 20, 2024 · 4 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@al-rosenthal
Copy link
Contributor

al-rosenthal commented Dec 20, 2024

Replication Procedure

  1. Connect to a wallet
  2. Issue a credential and accept invitation for credential on a device
  3. Send a proof request that does not contain any restrictions (restrictions array should remain empty)
  4. View the proof request details.

Observed Behavior

  • The credential 'card' is not rendered when a user is viewing the proof request details.

Expected output

  • The credential 'card' should render as expected when a proof does not contain any restricted schemas or credential definition ids
@al-rosenthal al-rosenthal added the bug Something isn't working label Dec 20, 2024
@al-rosenthal al-rosenthal self-assigned this Dec 20, 2024
@jeznorth
Copy link

@al-rosenthal can you provide an estimate here?

@jeznorth jeznorth changed the title Proof request card not rendering Proof Request 'Card' Not Rendering When Issued With No Restrictions Jan 20, 2025
@jeznorth
Copy link

@al-rosenthal to update ticket with steps to independently verify.

@al-rosenthal
Copy link
Contributor Author

Testing procedure:

  1. Create a traction sandbox tenant
  2. Open profile (top right icon) and become an issuer (person icon with +)
  3. Under configuration create new schema
  4. Under configuration create new credential definition for the schema you just created
  5. Under connections, create an invitation, scan QR code with BC wallet app
  6. Under connections, select connections, see the newly created connection and open the drop down, view raw content and copy the connection_id for later
  7. Issue credential to new connection in Issuance
  8. Navigate to developer page (icon in the top right)
  9. Scroll down and find Encoded JWT token, copy this for later
  10. In the browser navigate to: https://traction-sandbox-tenant-proxy.apps.silver.devops.gov.bc.ca/api/doc
  11. At the top of the page select ‘Authorize’ and type into the AuthorizationHeader section: Bearer {paste your JWT from earlier}, save and close the dialogue. It is important to note that Bearer is required and a space should be present between Bearer and the JWT token you copied from earlier
  12. Scroll down to /present-proof-2.0/send-request sand select ‘Try it out’ button
  13. Replace the example body with the following object: { "connection_id": “connection_id“, "presentation_request": { "indy": { "name": "Proof request", "version": "0.1", "requested_attributes": { "0_ssi_card": { "name": “name”, "restrictions": [] } }, "requested_predicates": {} } } }
  14. Replace the connection_id with the one you copied from earlier, you may also need to change the requested attribute to align with the schema created earlier
  15. Execute the request and wait to see proof request details on the device

@jeznorth jeznorth assigned jeznorth and unassigned al-rosenthal Jan 21, 2025
@jeznorth
Copy link

Self assign for QA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants