Traction Sandbox Hyperledger Aries/AnonCreds Workshop: FAQ, Questions and Troubleshooting

[swcurran]

This issue is for those running the Hyperledger Aries/AnonCreds Traction Sandbox Workshop to see an FAQ and to ask questions.

As we collect questions and develop answers, we'll add FAQs here. For now, there are none -- everything is working perfectly!

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.

[jgriffithGitHub]

I was able to run Lab 1, but for Lab 2, the "Add Schema form Ledger" button was disabled, so I couldn't run any other labs. What did I miss?

[swcurran]

Hi @jgriffithGitHub — try using this:CTD3jXaqbKyfyJh4WN7y1N:2:student id:1.0.0 — I think that should work. Please confirm and if it does, I’ll do a PR to update the docs. We recently changed the ledger that the Traction Instance points to, hence the issue.

[jgriffithGitHub]

I can't get to a screen where I can enter a value, so it's not a problem with a specific schema.
The button that displays that screen is disabled (see screenshot)

[swcurran]

Ah…sorry. Let me check. There might need to be an extra step in Lab 1. I’ll get back to you. Thanks for reporting this!

[swcurran]

@loneil — has something changed in the Sandbox deployment in the endorser handling?

[loneil]

Hi @jgriffithGitHub the step 4 in Lab1 ("Make your new Traction Tenant a verifiable credential issuer by:") must be completed before the ability to manage schemas and creds is available.

In the user Profile once you connect to the Endorser and Register the Public DID you should see the Issuer badge and the buttons will be available

[jgriffithGitHub]

Thanks.

…

On Wed, Apr 3, 2024 at 1:44 PM Stephen Curran ***@***.***> wrote: Ah…sorry. Let me check. There might need to be an extra step in Lab 1. I’ll get back to you. Thanks for reporting this! — Reply to this email directly, view it on GitHub <#927 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABZQEBLDMBRT2QMYGPH7DTLY3REZFAVCNFSM6AAAAAA7W55I42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZVGMZTQNZVGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[jgriffithGitHub]

I see what I missed.. I had to click on the icon in the left-most column. I was clicking on the words "bcovrin-test" which wasn't doing anything. Thanks for the quick replies.

…

On Wed, Apr 3, 2024 at 1:51 PM loneil ***@***.***> wrote: Hi @jgriffithGitHub <https://github.com/jgriffithGitHub> the step 4 in Lab1 ("Make your new Traction Tenant a verifiable credential issuer by:") must be completed before the ability to manage schemas and creds is available. In the user Profile once you connect to the Endorser and Register the Public DID you should see the Issuer badge and the buttons will be available image.png (view on web) <https://github.com/bcgov/traction/assets/17445138/f5f73d54-ac9a-4b77-a422-8b5655194a7c> — Reply to this email directly, view it on GitHub <#927 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABZQEBNAVOMEBD5MEQJL2CLY3RFTXAVCNFSM6AAAAAA7W55I42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZVGM2TEMJVGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[swcurran]

Did the schema in the tutorial work? I didn’t see it when I checked, but I might have rushed it. Or did you use the one I posted above?

[jgriffithGitHub]

The schema in the lab worked.

H7W22uhD4ueQdGaGeiCgaM:2:student id:1.0.0

I was able to work through the labs with it.

[swcurran]

Awesome — thanks. Closing this issue. Should probably add a note in the document about this via a PR.

[icredyRepo]

Is there a change in BCcovrin network to accept the new endorser and agents ?
I have installed local sandbox environment of TRACTION https://github.com/bcgov/traction?tab=readme-ov-file. The Aca-py Version 1.0 was working fine. I was able to connect to Tenant to the Endorser agent and issue schemas to the bcovrin ledger. But just recently that version stopped working. When i create a new tenant and try to connect to endorser from profile option of the tenant UI i get the message that ,request is set, but tenant is not connected to endorser.
To investigate further i tried to establish connection between tenant Agent and Endorser agent through there swaggers and what i found is the connection request is sent by tenant (tenant/endorser-connection) and as a response i got a following response. According to this it seems that the accept is set as manual and not sure why is that because the Agent config file based on which endorser container was build has a auto-accept- connection request set as true.
I have tried the same with latest version of traction where agents are upgraded to version 1.1.0 and have the same behaviour.
{
"state": "request",
"created_at": "2024-12-10T04:57:06.625901Z",
"updated_at": "2024-12-10T04:57:06.650905Z",
"connection_id": "a6b09e33-ed27-490b-93c5-ba35b5f6729c",
"my_did": "DzTXxYKShHZxxGVEtySUbc",
"their_did": "SVfHGCEEvEFmpBPcxgNqRR",
"their_role": "inviter",
"connection_protocol": "didexchange/1.0",
"rfc23_state": "request-sent",
"request_id": "216fd327-9598-4906-9a8e-df6ab83ead0d",
"accept": "manual",
"invitation_mode": "once",
"alias": "bcovrin-test-endorser",
"their_public_did": "SVfHGCEEvEFmpBPcxgNqRR"
}

[swcurran]

FYI @WadeBarnes and @loneil — please take a look at the previous comment

[esune]

@icredyRepo I checked out the latest main (d422ebce8ec86149ce24b797e82bf2e29fe4e1c6) and tested creating a tenant and connecting to an endorser: everything works as expected.
Please note that bcovrin-test-endorser in the list is set as "quick-connect" (little lightning bolt besides it), so the tenant UI will automatically refresh and publish a did automatically, while bcovrin-test-endorser-1 will require you to manually refresh the view to see if the connection is active, and you will have to trigger the public did promotion as well.

If your setup does not work, please check that all your containers are running and that your ngrok tunnel is active - it becomes stale after some time.

If you still need support feel free to log a new issue - this was related to a workshop that happened a few months back and used a hosted version of Traction (https://traction-sandbox-tenant-ui.apps.silver.devops.gov.bc.ca) and not to the actual code.

[ananyachibber21]

When we are establishing connection between 2 tractions agents a DID SaTmbLi9ScaHZv5Sn6VBdJ is created. As i understand the connection DID's should not be written in ledger and hence can't be resolved.
To test if this DID is resolvable i used api GET/resolver/resolve/{did} and put did:sov:SaTmbLi9ScaHZv5Sn6VBdJ and below is the DIDDoc.
So my question is why this DID got resolved if the connections DID's are not suppose to be resolvable.

{
"did_document": {
"@context": "https://w3id.org/did/v1",
"id": "did:sov:SaTmbLi9ScaHZv5Sn6VBdJ",
"authentication": [
"did:sov:SaTmbLi9ScaHZv5Sn6VBdJ#1"
],
"service": [
{
"id": "did:sov:SaTmbLi9ScaHZv5Sn6VBdJ#didcomm-0",
"type": "did-communication",
"priority": 0,
"recipientKeys": [
"did:sov:SaTmbLi9ScaHZv5Sn6VBdJ#1"
],
"serviceEndpoint": "https://traction-sandbox-acapy.apps.silver.devops.gov.bc.ca"
}
],
"verificationMethod": [
{
"id": "did:sov:SaTmbLi9ScaHZv5Sn6VBdJ#1",
"type": "Ed25519VerificationKey2018",
"controller": "did:sov:SaTmbLi9ScaHZv5Sn6VBdJ",
"publicKeyBase58": "EwY9KhCGnkbgPsSbyXRLQbnziaZXnP1J91TVrKSLa5T4"
}
]
},
"metadata": {
"resolver_type": "native",
"resolver": "LegacyPeerDIDResolver",
"retrieved_time": "2024-12-18T05:14:18Z",
"duration": 28
}
}

[icredyRepo]

@icredyRepo I checked out the latest main (d422ebce8ec86149ce24b797e82bf2e29fe4e1c6) and tested creating a tenant and connecting to an endorser: everything works as expected. Please note that bcovrin-test-endorser in the list is set as "quick-connect" (little lightning bolt besides it), so the tenant UI will automatically refresh and publish a did automatically, while bcovrin-test-endorser-1 will require you to manually refresh the view to see if the connection is active, and you will have to trigger the public did promotion as well.

If your setup does not work, please check that all your containers are running and that your ngrok tunnel is active - it becomes stale after some time.

If you still need support feel free to log a new issue - this was related to a workshop that happened a few months back and used a hosted version of Traction (https://traction-sandbox-tenant-ui.apps.silver.devops.gov.bc.ca) and not to the actual code.

Hi

@icredyRepo I checked out the latest main (d422ebce8ec86149ce24b797e82bf2e29fe4e1c6) and tested creating a tenant and connecting to an endorser: everything works as expected. Please note that bcovrin-test-endorser in the list is set as "quick-connect" (little lightning bolt besides it), so the tenant UI will automatically refresh and publish a did automatically, while bcovrin-test-endorser-1 will require you to manually refresh the view to see if the connection is active, and you will have to trigger the public did promotion as well.

If your setup does not work, please check that all your containers are running and that your ngrok tunnel is active - it becomes stale after some time.

If you still need support feel free to log a new issue - this was related to a workshop that happened a few months back and used a hosted version of Traction (https://traction-sandbox-tenant-ui.apps.silver.devops.gov.bc.ca) and not to the actual code.

Hi Esun,
I have check all the containers are up and running. Traction agent swagger is running at port 9301 i can unlock API's using change-me password. But still i am not able to connect to endorser from Profile of Traction Tenant. Following is the error i am getting.

[esune]

@ananyachibber21 if the did was used to establish a connection, it WILL be resolvable by the other agent since they know where that did comes from. Your question is likely better suited for the OWF Discord aca-py channel since it is not related to Traction specifically: (join from here and search for the right channel.

@icredyRepo if your containers have been running for a long time, your ngrok tunnel may have expired and you will have to restart the services to refresh it. Also make sure you have a valid NGROK_AUTHTOKEN in your .env file. If you need more help on this, please open a separate issue.