Update OID4VC section #12
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ssteinbuss
reviewed
Jun 13, 2025
|
|
||
| ## OpenID for Verifiable Credentials (OID4VC) | ||
| Founded in 2007, the OpenID Foundation (OIDF) is a global open standards body committed to helping __people__ assert their identity wherever they choose. | ||
| Founded in 2007, the OpenID Foundation (OIDF) is a global open standards body with the mission to lead the global community in creating identity standards that are secure, interoperable and privacy-preserving. |
Member
There was a problem hiding this comment.
Not accepted. This is not a document for marketing purposes.
ssteinbuss
reviewed
Jun 13, 2025
| - Self-Issued OpenID Provider v2 (SIOPv2) | ||
| - OpenID for Verifiable Presentations over BLE | ||
| - OpenID Connect UserInfo Verifiable Credentials | ||
| The OpenID Digital Credentials Protocols (DCP) working group goal is to develop OpenID specifications for the Issuer-Holder-Verifier-Model use-cases to enable issuance and presentations of the Digital Credentials of any format (W3C VCs, IETF SD-JWT VCs, ISO/IEC 18013-5, etc.) and pseudonymous authentication from the End-User to the Verifier. |
Member
There was a problem hiding this comment.
Not accepted, no added value in relation to the text before.
ssteinbuss
reviewed
Jun 13, 2025
| The OpenID Digital Credentials Protocols (DCP) working group goal is to develop OpenID specifications for the Issuer-Holder-Verifier-Model use-cases to enable issuance and presentations of the Digital Credentials of any format (W3C VCs, IETF SD-JWT VCs, ISO/IEC 18013-5, etc.) and pseudonymous authentication from the End-User to the Verifier. | ||
|
|
||
| The [OID4VC Issuance specification](https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-wg-draft.html) defines an OAuth-protected API for the issuance of Verifiable Credentials. It allows a Credential Issuer to assert End-User claims. Verifiable Credentials can be securely presented for the End-User to the Resource Provider, without involvement of the credential issuer. | ||
| From the DCP working group is developed the OpenID for Verifiable Credential Issuance (OID4VCI) and the OpenID for Verifiable Presentations (OID4VP), commonly refered as OID4VC |
Member
There was a problem hiding this comment.
Not accepted, no added value in relation to the text before.
ssteinbuss
reviewed
Jun 13, 2025
| From the DCP working group is developed the OpenID for Verifiable Credential Issuance (OID4VCI) and the OpenID for Verifiable Presentations (OID4VP), commonly refered as OID4VC | ||
|
|
||
| It requires an End-User Wallet as the store in which the holder can request, receive, store, present and manage Verifiable Credentials and cryptographic key material. | ||
| The [OID4VC Issuance specification](https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-wg-draft.html) defines an OAuth-protected API for the issuance of Verifiable Credentials. It allows a Credential Issuer to assert an optional access token, which depending on the type and characteristics of the token can require a human interaction. Verifiable Credentials can be securely presented for the End-User to the Resource Provider, without involvement of the credential issuer. |
Member
There was a problem hiding this comment.
Not accepted, no added value in relation to the text before.
ssteinbuss
reviewed
Jun 13, 2025
| The [OID4VC Issuance specification](https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-wg-draft.html) defines an OAuth-protected API for the issuance of Verifiable Credentials. It allows a Credential Issuer to assert an optional access token, which depending on the type and characteristics of the token can require a human interaction. Verifiable Credentials can be securely presented for the End-User to the Resource Provider, without involvement of the credential issuer. | ||
|
|
||
| The [OID4VP specification](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html) defines a mechanism on top of OAuth 2.0 to request and present Verifiable Credentials as Verifiable Presentations. It introduces the VP Token as a container to enable End-Users to present Verifiable Presentations to Verifiers using a Wallet. The specification is an extension of OpenID Connect to allow presentation of claims in the form of W3C Verifiable Credentials as part of the protocol flow. | ||
|  |
Member
There was a problem hiding this comment.
Cannot be accepted for IPR reasons. Unclear provenance.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
in the context of #8
update workflow and properties of OID4VCi and OID4VP