Introducing an authentication middleware #802
DaevMithran
started this conversation in
Ideas
Replies: 1 comment
-
|
Hi @DaevMithran, it is definitely something we can support. For the naming convention, we currently do not support named agents beyond HTTPs well-known names which we are in the process of finishing up. For W3C VC Format we may need to add support for signing and verification of records, alongside naming support, since currently this is not yet supported. This can be added as a standalone component to support your use-case and we would be happy to help. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
we at Cheqd are hosting a directory. we would like to propose an authentication middleware for directories to customize the permissions to write.
At cheqd we will be validating the signatures of the oasf matching with the issuer's did-documents keys on-chain and, anyone can publish an oasf record as long as the issuer DID is on-chain is our idea. Happy to hear some feedback and thoughts into this.
Questions:
What are the disadvantages of using W3C VC Format for an oasf record within the directory? Will it affect the indexing?
Beta Was this translation helpful? Give feedback.
All reactions