jamshale

@ianco This env variable was overriding the command line argument. https://github.com/hyperledger/aries-cloudagent-python/blob/main/docker/Dockerfile.demo#L7 And then I also commented out the command line argument https://github.com/hyperledger/aries-cloudagent-python/blob/main/demo/runners/support/agent.py#L588

I think we can ignore the security issue reported. It's to do with running the demo image as root user.

I was trying to just allow anything here because I didn't know what type of pattern we could use. I don't think we can have the numbers `:2,:3,:4` in the...

I couldn't replicate this but maybe I'm creating the qualified did differently. Could you provide the steps you took to generate the fully qualified did:sov?

> ^ Looks like the strip_did_prefix was added recently. So the code I'm viewing is probably not what you're running with version 1.2.0. > > Meaning that the qualified did...

I'm still not able to re-produce with this type of did. I have been able to get the same behavior by altering the did record in the local wallet. Did...

So... I should have tried to do this earlier but I confirmed this error happens on version 1.2.0, but does not happen on main. I predict that running your test...

I've been thinking about this and I don't think qualified did:sov`s are currently supported by anoncreds. The implementation was for legacy indy which considered the unqualified version only. I'm sure...

I think it allows you to create the schema but then the schema_id has did:sov at the front and if you try and use this when creating a cred_def or...

We'll need to do this as a feature. Support qualified did sov's in anoncreds legacy_indy registry. I can probably try and get to it, I'm currently studying all the required...