Yuki I

What was the motivation for custom endpoints that couldn't be fulfilled used in the built in?

It is an interesting implementation because the current implementation also return misleading endpoints because it uses the standard configuration path - `/.well-known/openid-configuration`. It would appear that a prefix to the...

Any movement on this issue?

Did anyone ever find a solution for this. I'm currently having troubles integrating acapy with Hashicorp vault secrets management because the provisioned database throws the error ```aries_askar.error.AskarError: Backend error Caused...

> You've done a ton of investigation and debugging -- thank you! > > I'd like to understand more of what's going on here. > > Passing a profile to...

Can this be merged now pending a preferred resolution?

Yes it is specific to the multi-ledger configuration scenario. Also are you referring to inline comments? Or does this pr + issue suffice?

**Status Update**: After days of debugging, I’m still stuck. The error persists when revocation is enabled in multitenant setups and `askar-anoncreds` wallet types. Here’s the simplest breakdown: ### **What Happens**...

Full context of the error logs before failure: ```python DEBUG /acapy_agent/anoncreds/revocation.py:396 ENTER: create_and_register_revocation_list() - RevRegDef ID: RANDOM2025DIDRANDOM101:4:RANDOM2025DIDRANDOM101:3:CL:2738835:random1:CL_ACCUM:1, Options: {'revocation_registry_size': 100, 'support_revocation': True} DEBUG /acapy_agent/anoncreds/revocation.py:402 Create and register revocation list profile:...

Edits to generate logs: ```python # acapy_agent/anoncreds/revocation_setup.py async def on_rev_reg_def(self, profile: Profile, event: RevRegDefFinishedEvent): """Handle rev reg def finished.""" payload = event.payload # --- Detailed Logging START --- LOGGER.debug("=" *...