How to properly enable Anoncreds

[sanderPostma]

The scope of a project I am working on is limited to Anoncreds only. I see separate endpoints in the API spec for Anoncreds support. But when I try to call them I get an error

403: AnonCreds interface requires AskarAnoncreds profile

I have tried to set wallet type in default.yml and in .env ACAPY_WALLET_TYPE=askar-anoncreds. After that I can call the Anoncreds endpoints, but now I have issues in other parts of Traction. I can't even log in the tenant UI anymore. In the Traction agent log I see:

traction-agent-1  |   File "/home/aries/.venv/lib/python3.12/site-packages/acapy_agent/ledger/multiple_ledger/manager_provider.py", line 46, in provide
traction-agent-1  |     raise MultipleLedgerManagerError(
traction-agent-1  | acapy_agent.ledger.multiple_ledger.base_manager.MultipleLedgerManagerError: Unexpected wallet backend: askar-anoncreds

Are there other variables I need to modify to make this work?

[swcurran]

See this article here for details: https://aca-py.org/latest/deploying/AnonCredsWalletType/

Short summary — you are using the wallet type “askar” that supports and uses AnonCreds VCs, but does it with an older library. These are often called Indy Credentials, even though the operate exactly as AnonCreds. When you use that wallet type, you use the older endpoints.

If you control the Traction instance, change the ACA-Py start up to use wallet-type “askar-anoncreds” and then use the “anoncreds” endpoints.