fix: remove well-known from Issuer Metadata API #180
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WHAT
Distinguish Issuer Metadata API based on whether sub-paths are included in the Issuer base URL.
If no sub-path is available, a
.well-known
must be used. If a sub-path is available, the Issuer Metadata API must be hosted without.well-known
and aIssuerMetadataService
DID service must be addedCloses #173
How was the issue fixed?
Update Issuance protocol specification and added
IssuerMetadataService
entry in the JSON-LD contextMore context
The Issuer may decide on including the
IssuerMetadataService
DID service even if it is provided under a well known endpoint, but for the spec its probably better to not include this.