-
Notifications
You must be signed in to change notification settings - Fork 15
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
Expand DID Configuration to handle more DID-related config items #37
Comments
The current resource structure: {
"@context": "https://identity.foundation/.well-known/contexts/did-configuration-v0.0.jsonld",
"entries": [ VC_DATA_MODELs ]
} Proposed structure: {
"@context": "https://identity.foundation/.well-known/contexts/did-configuration-v0.0.jsonld",
"linked_dids": [ VC_DATA_MODELs ],
"supported_protocols": [ PROTOCOLs],
"credential_manifests": [ CREDENTIAL_MANIFESTS]
} |
potential issue is that the supported protocols implicitly apply to all linked dids... |
Link to related hackmd...https://hackmd.io/QCJ3WDcLSXWp8t3hAQ387A |
Good point - I wonder if there would need to be something in the issuance flow that specifies which DID the user wants to have a given cred issued from? |
We can resolve this issue by adding a member of the |
protocol data model...
additional properties false, really don't want people to overload that object. |
Resolved:
|
well known did configuration now blocked by: |
I would only be in favor of adding URLs at this time, this issue is going to stick aroudn until we decide which URLs to add or we close this issue :) |
As we look at how to make Credential Manifests discoverable, we have an opportunity to reuse the DID Configuration resource as the place to do that, as well as the things related to it. This might include a list of CMs (or references to them), details about issuance protocols (OIDC endpoints, DIDComms connection details, etc.). I think reusing this for more config stuff makes sense, given it is appropriately named/situated.
The text was updated successfully, but these errors were encountered: