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
feat: builder pattern for id_token and response (#26)
* Add support for Request by reference
Add tests for RequestUrl
Add missing request parameters
Add sphereon demo website test
Update documentation with new RequestUrl
Remove sphereon demo example
Add validate_request method to Provider struct
Add preoper Ser and De for SiopRequest and RequestBuilder
Add skeptic for Markdown code testing
Add support for Request by reference
fix: fix rebase conflicts
Add comments and fix some tests
fix: Move `derivative` to dev-dependencies
Refactor Provider and Subject
improve tests and example using wiremock
Improve struct field serde
fix: remove claims from lib.rs
style: fix arguments order
Add did:key DID method
Add support for Request by reference
fix: Remove lifetime annotations
Add preoper Ser and De for SiopRequest and RequestBuilder
Add Scope and Claim
fix: fix rebase conflicts
* Improve struct field serde
* fix: remove custom serde
* Add claims and scope parameters
* Add Storage and RelyingParty test improvement
* Update README example
* fix: Add standard_claims to test IdToken
* Move Storage trait to test_utils
* Remove storage.rs
* fix: fix dev-dependencies
* fix: fex rebase to dev
* fix: fix rebase to dev
* feat: add Claim trait with associated types
* fix: build
* fix: remove build.rs and change crate name in doc tests
* feat: refactor claims.rs
* feat: Add builder for Response and IdToken
* fix: silence clippy warning
* feat: add missing ID Token claim parameters
* fix: remove skeptic crate
* feat: allow json arguments for claims() method
* fix: replace unwraps
* style: add specific request folder
* fix: undo unnecassary cloning
* style: explicit serde_json usage
* test: improve RequestBuilder tests
* fix: fix rebase
* style: Rename SiopRequest and add comments
* style: rename Request and Response
* style: remove whitespace
Copy file name to clipboardExpand all lines: README.md
+28-28
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,9 @@ OpenID for Verifiable Credentials (OID4VC) consists of the following specificati
16
16
17
17
Currently the Implicit Flow is consists of four major parts:
18
18
19
-
- A `Provider` that can accept a `SiopRequest` and generate a `SiopResponse` by creating an `IdToken`, adding its key identifier to the header of the `id_token`, signing the `id_token` and wrap it into a `SiopResponse`. It can also send the `SiopResponse` using the `redirect_uri` parameter.
20
-
- A `RelyingParty` struct which can validate a `SiopResponse` by validating its `IdToken` using a key identifier (which is extracted from the `id_token`) and its public key.
21
-
- The `Subject` trait can be implemented on a custom struct representing the signing logic of a DID method. A `Provider` can ingest an object that implements the `Subject` trait so that during generation of a `SiopResponse` the DID method syntax, key identifier and signing method of the specific `Subject` can be used.
19
+
- A `Provider` that can accept a `AuthorizationRequest` and generate a `AuthorizationResponse` by creating an `IdToken`, adding its key identifier to the header of the `id_token`, signing the `id_token` and wrap it into a `AuthorizationResponse`. It can also send the `AuthorizationResponse` using the `redirect_uri` parameter.
20
+
- A `RelyingParty` struct which can validate a `AuthorizationResponse` by validating its `IdToken` using a key identifier (which is extracted from the `id_token`) and its public key.
21
+
- The `Subject` trait can be implemented on a custom struct representing the signing logic of a DID method. A `Provider` can ingest an object that implements the `Subject` trait so that during generation of a `AuthorizationResponse` the DID method syntax, key identifier and signing method of the specific `Subject` can be used.
22
22
- The `Validator` trait can be implemented on a custom struct representing the validating logic of a DID method. When ingested by a `RelyingParty`, it can resolve the public key that is needed for validating an `IdToken`.
/// An individual claim request as defined in [OpenID Connect Core 1.0, section 5.5.1](https://openid.net/specs/openid-connect-core-1_0.html#IndividualClaimsRequests).
99
105
/// Individual claims can be requested by simply some key with a `null` value, or by using the `essential`, `value`,
100
106
/// and `values` fields. Additional information about the requested claim MAY be added to the claim request. This
@@ -128,7 +134,7 @@ pub type StandardClaimsValues = StandardClaims<ClaimValue<()>>;
128
134
/// This struct represents the standard claims as defined in the
0 commit comments