search

openid / OpenID4VP

59 stars 20 forks source link

Adding DID service endpoint type to spec #47

Closed OIDF-automation closed 7 months ago

OIDF-automation commented 1 year ago

Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/1934

Original Reporter: EECC

For further supporting DIDs, a PR for https://www.w3.org/TR/did-spec-registries/#serviceendpoint has been created, announcing the the OpenID4VC discovery (.well-known/oauth-authorization-server|openid-credential-issuer) endpoints within the DID document.

‌

In the PR the necessary context is currently hosted at our company, but it would be advisable to host it on openid.net or their Github page respectively. Additionally the sources in the context document should be checked; especially for oauth-authorization-server as it is not described in the OPenID4VC spec.

‌

When accepted, this should be integrated in the OpenID4VC specs. Till then i ask for review and feedback on the PR for the W3C DID spec: https://github.com/w3c/did-spec-registries/pull/513

‌

OIDF-automation commented 1 year ago

Imported from AB/Connect bitbucket - Original Commenter: mbj

Submitted -> New

OIDF-automation commented 1 year ago

Imported from AB/Connect bitbucket - Original Commenter: EECC

Already merged https://w3c.github.io/did-spec-registries/#openid4-verifiable-presentation

Sakurann commented 1 year ago

If I understand correctly, the request is to define which path must be used to obtain wallet's metadata and add that to the wallet-invocation section of OID4VP. because wallet is acting as an AS, .well-known/oauth-authorization-server might be best suited even if feels counterintuitive...

Sakurann commented 8 months ago

@F-Node-Karlsruhe I see the PR you reference has been merged. does not have a precedent of are there any other action item here or can this issue be closed?

I think you were also asking OIDF to host @context but that seems to be specific to the credential format, so w3.org sounds like a better place? i don't think OIDF has a precedent of hosting files like this cc (@jogu), so uploading it to this GH would be much simpler..

jogu commented 8 months ago

As policy from the board OIDF generally doesn't host registries as others like IANA (or perhaps W3C, I don't know?) are better setup for that. That said I do not understand the exact ask here and don't follow how it relates to the content of the PR that was merged.

F-Node-Karlsruhe commented 7 months ago

This request is about referencing the spec of the respective endpoints when publishing them in a DID document.

The current context is very small with a link to the OID4VC spec: https://ssi.eecc.de/api/registry/context/openid4vc

It just would be nicer if the context was hosted on openid.net but we could also simply put it on IPFS or github as well.

awoie commented 7 months ago

@F-Node-Karlsruhe Normally, people interested in making JSON-LD context of their spec available to the public is to host the context-related files where the specification lives, e.g., github, and then register a permalink through w3id.org to have a prettier URL. I would suggest doing the same for this.