-
Notifications
You must be signed in to change notification settings - Fork 520
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to fetch credential definition details from ledger using did:web #3544
Comments
Might be related to #3462 |
You shouldn't set a did:web to the public did. It is very indy specific right now. This should be prevented. There is ongoing work to allow the public did to be different types and not interfere with did:indy operations, but it isn't going to be completed for some time. However, it shouldn't fail to read the indy ledger because of an invalid public did so this should still be looked at. I'm not aware of why it tries to use the public did when reading the indy ledger. |
@NB-PrasadKatkar can you provide examples of how:
I did some quick testing using Traction Sandbox:
@jamshale 's recommendation still stands, but trying to pinpoint what might be going wrong in your case in order to determine the course of action in ACA-Py |
Description
I am trying to fetch a credential definition from the ledger using the HTTP GET endpoint:
/credential-definitions/{cred_def_id}
My agent is running on the latest ACA-Py release and is configured with a
did:web
as the public DID. When attempting to retrieve the credential definition, ACA-Py tries to resolve the public DID but fails, resulting in the following error:indy_vdr.error.VdrError: Request failed: client request invalid: InvalidClientRequest('prasad.github.io', 1739295285303260321, "validation error [SafeRequest]: should not contain the following chars ['.'] (identifier=prasad.github.io)")
Steps to Reproduce
/credential-definitions/{cred_def_id}
.did:web
.Environment
v1.2.2
did:web
Bcovrin test
Docker
Additional Context
Any insights into resolving this issue or potential workarounds would be appreciated.
The text was updated successfully, but these errors were encountered: