Set default endorser in helm value

[loneil]

In values.yaml the ledger/endorser default setup is

  ## Acapy multiledger configuration file
  ## @param acapy.ledgers.yml [object] YAML configuration for connecting to multiple HyperLedger
  ##
  ledgers.yml:
    - id: bcovrin-test
      is_production: true
      is_write: true
      genesis_url: "http://test.bcovrin.vonx.io/genesis"
      endorser_did: "Ket75eV5UQvVkW2XBjgDH7"
      endorser_alias: "bcovrin-test-endorser"

Ket75eV5UQvVkW2XBjgDH7 is not a valid endorser any more (was the old one in tools).

Should set this to one that can be used? I think? Is it ok for us to put the DID for our auto-everything sandbox bcovrin-test endorser in here as default config? cc @esune

[esune]

+1 to using the automated endorser on BCovrin test for the default chart

[H4LL]

Hey, I'm trying to run through an end to end demo. I'm debugging why the scheme creation isn't working and I suspect this issue is the culprit.

Does anyone have a workaround for this in the meantime? Also, I'm wondering if there is a forum where I can ask general questions like this about traction (like Linux Foundation Decentralised Trust on Discord).

[loneil]

Hey, I'm trying to run through an end to end demo. I'm debugging why the scheme creation isn't working and I suspect this issue is the culprit.

Does anyone have a workaround for this in the meantime? Also, I'm wondering if there is a forum where I can ask general questions like this about traction (like Linux Foundation Decentralised Trust on Discord).

If running locally with docker then this issue wouldn't be releated as this applies to the Helm charts for deploying to Kubernetes, and which cloud-hosted Endorser would be default for attempting connections.

The local docker setup, if running the compose script up, will stand up a local endorser and the Traction (ACA-Py) agent is set to allow connections to that local endorser.

If that screenshot there is from running the Tenant UI, then that 404 on the Endorser Connection (if indeed running locally) would be expected (maybe we should not have it console error for this reason...) and schema creation or other ledger write operations would not be able to proceed until the Endorser allows it. On local docker this is all set up to auto allow writes but the Endorser connection and DID registration are required for each tennat before that can go on

Locally, you should be able to connect to the Endorser and set the write ledger through the Tenant UI in Profile. The step 4 in this Lab 1 https://aca-py.org/latest/demo/Aries-Workshop/#lab-1-steps-to-follow describes those steps.

(There's also the "Make Tenant an Issuer" video here https://github.com/bcgov/traction/blob/main/docs/USE-CASE-ONBOARD.md#make-teanant-an-issuer but I need to re-record that as the UI has changed since then, but the general concept in the Tenant UI is the same)

[H4LL]

Hey, thanks for the response! I appreciate it. I have actually went through the make tenant an issuer phase. I can write credentials to the ledger using pre-written schemes but it seems not schemes. The 'Create Scheme' button is allowed and I can go through the menu but there is no visible action after I press the button to create.

I actually hadn't seen that Aries workshop and I've been messing around with Bifold too so that will be incredibly useful as a precedent for them working together. At the moment though I'm trying to run through this with Alice and Bob as tenants where Alice is issuing credentials to Bob and then Bob is verifying via the tenant UI. Is that currently possible through the UI? I don't seem to have any option to respond to the verification for my previously issued credential request as Bob:

I appreciate this may not be the forum for this. If you think it's worthwhile I can make an issue for it. It'd also be great to know if theres a more appropriate place I can take questions like this to.

Thanks again!

[loneil]

Hi @H4LL no prob. I think I see the issue for schemas, if it's just that nothing happens when the button is clicked it's just a frontend validation problem

schema versions must be in the form of X.X or X.X.X for Aries, so you'd want to put something like 1.0.0 there. This should be validated on the UI and tell you that but something appears to have recently broken on that screen... I'll fix that up shortly (tracking here #1382). Thanks for finding!

I actually hadn't seen that Aries workshop and I've been messing around with Bifold too so that will be incredibly useful as a precedent for them working together. At the moment though I'm trying to run through this with Alice and Bob as tenants where Alice is issuing credentials to Bob and then Bob is verifying via the tenant UI. Is that currently possible through the UI? I don't seem to have any option to respond to the verification for my previously issued credential request as Bob:

This feature isn't in the Tenant UI yet, if it's a use case that could be useful then yeah creating an issue in this repo to request it would be great.

[loneil]

@H4LL for discussion places

Also, I'm wondering if there is a forum where I can ask general questions like this about traction (like Linux Foundation Decentralised Trust on Discord).

We talked about this internally the other day and since Traction is built on top of ACA-Py, and the Traction maintainers are active in the ACA-Py community then questions could be posed on that Discord. Note ACA-Py is (at this exact time) moving from the Linix Foundation Decentralized Trust to the OpenWallet Foundation, so some communication platforms are just getting set up now. The link to the OWF Discord can be found here: https://github.com/openwallet-foundation/acapy?tab=readme-ov-file#troubleshooting