Closed borisrizov-zf closed 2 months ago
Hi @borisrizov-zf , please note that serviceEndpoint
should be the base url. So the end url for presentation query should look like: {serviceEndpoint}/presentations/query
.
If serviceEndpoint has value https://<miw_host>/api/token
, then presentation query endpoint will be https://<miw_host>/api/token/presentations/query
.
May be serviceEndpoint should have value https://<miw_host>/api
so that presentation query endpoint looks like https://<miw_host>/api/presentations/query
.
Hi @hemantxpatel, these are two different service
entries imo. One is the SecurityTokenService
and one is the CredentialService
. The former has the service URL /api/token
and the ladder /presentations/query
. That would be reasonable?
I've updated the description, to account for both.
Hi @borisrizov-zf , that's correct. Only thing is /presentations/query
should not be part of the serviceEndpoint
as it is appended by EDC.
It should look like this:
"service": [
{
"id": "did:web:<miw_specific_id>#SecurityTokenService",
"type": "SecurityTokenService",
"serviceEndpoint": "https://<miw_host>/api/token"
},
{
"id": "did:web:<miw_specific_id>#CredentialService",
"type": "CredentialService",
"serviceEndpoint": "https://<miw_host>"
}
],
@hemantxpatel Ah, thanks for the heads up, I'll update that this week.
Description
The
service
key for the credential service must be present in the DID document of all did subjects, but it is currently missing.Acceptance Criteria
service
key to the DID documentservice
key is a set/list of service entriesid
,type
andserviceEndpoint
serviceEndpoint
is to be a valid URI (the mapping and list/set variants can be omitted)/<bpn>/did.json
will include this new service entryAdditional Information
The types of service fields are described here: https://www.w3.org/TR/did-core/#services
Example service entry: