You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
_IMPORTANT the packages are still in an early development stage, as such breaking changes are to be expected_
10
+
_IMPORTANT the packages are still in an early development stage, which means that breaking changes are to be expected_
11
11
12
12
# Background
13
13
@@ -19,10 +19,10 @@ OpenID4VCI defines an API designated as Credential Endpoint that is used to issu
19
19
corresponding OAuth 2.0 based authorization mechanisms (see [RFC6749]) that a Wallet uses to obtain authorization to
20
20
receive verifiable credentials. W3C formats as well as other Credential formats are supported. This allows existing
21
21
OAuth 2.0 deployments and OpenID Connect OPs (see [OpenID.Core]) to extend their service and become Credential Issuers.
22
-
It also allows new applications built using Verifiable Credentials to utilize OAuth 2.0 as integration and
22
+
It also allows new applications built using Verifiable Credentials to utilize OAuth 2.0 as an integration and
23
23
interoperability layer. This package provides holder/wallet support to interact with OpenID4VCI capable Issuer systems.
24
24
25
-
Next to the client and issuer, there is also a common package, which has all the types and payloads shared between the client and issuer.
25
+
In addition to the client and issuer, there is also a common package, which has all the types and payloads shared between the client and issuer.
26
26
27
27
# Packages
28
28
There are 2 main packages in this mono-repository
@@ -34,7 +34,7 @@ The OpenID4VCI client is typically used in wallet type of applications, where th
34
34
## OpenID for VCI Issuer
35
35
36
36
The OpenID4VCI issuer is used in issuer type applications, where an organization is issuing the credential(s). More info can be found in the issuer [README](./packages/issuer/README.md).
37
-
Please not that the Issuer is a library. It has some examples how to run it with REST endpoints. If you however are looking for a full solution we suggest our [SSI SDK](https://github.com/Sphereon-Opensource/ssi-sdk) or the [demo](https://github.com/Sphereon-Opensource/OID4VC-demo)
37
+
Please note that the Issuer is a library. It has some examples on how to run it with REST endpoints. If you are however looking for a full solution we suggest our [SSI SDK](https://github.com/Sphereon-Opensource/ssi-sdk) or the [demo](https://github.com/Sphereon-Opensource/OID4VC-demo)
38
38
39
39
40
40
# Flows
@@ -47,9 +47,9 @@ This flow is supported but might need more work, so you might run into issues tr
47
47
48
48
## Pre-authorized Code Flow
49
49
50
-
The pre-authorized code flow assumes the user is using an out of bound mechanism outside the issuance flow to
50
+
The pre-authorized code flow assumes that the user is using an out of bound mechanism outside the issuance flow to
51
51
authenticate first.
52
52
53
-
The below diagram shows the steps involved in the pre-authorized code flow. Note that wallet inner functionalities (like
54
-
saving VCs) are out of scope for this library. Also This library doesn't involve any functionalities of a VC Issuer
53
+
The below diagram shows the steps involved in the pre-authorized code flow. Note that inner wallet functionalities (like
54
+
saving VCs) are out of scope for this library. Also This library doesn't include any functionalities of a VC Issuer
0 commit comments