Skip to content

Commit

Permalink
Merge pull request #118 from italia/fix-client-assertion-type
Browse files Browse the repository at this point in the history
Fix client assertion type
  • Loading branch information
peppelinux authored Sep 6, 2023
2 parents 697356d + afe31aa commit d7a7f59
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 5 deletions.
6 changes: 3 additions & 3 deletions docs/en/pid-eaa-issuance.rst
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ Below a non-normative example of the PAR.
&code_challenge=E9Melhoa2OwvFrEMTJguCHaoeK1t8URWbuGJSstw-cM
&code_challenge_method=S256
&request=eyJhbGciOiJSUzI1NiIsImtpZCI6ImsyYmRjIn0.ew0KIC Jpc3MiOiAiczZCaGRSa3F0MyIsDQogImF1ZCI6ICJodHRwczovL3NlcnZlci5leGFtcGxlLmNvbSIsDQo gInJlc3BvbnNlX3R5cGUiOiAiY29kZSBpZF90b2tlbiIsDQogImNsaWVudF9pZCI6ICJzNkJoZFJrcXQz IiwNCiAicmVkaXJlY3RfdXJpIjogImh0dHBzOi8vY2xpZW50LmV4YW1...
&client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-key-attestation
&client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-client-attestation
&client_assertion=$WalletInstanceAttestation$
The JWS header of request object is represented below:
Expand Down Expand Up @@ -141,7 +141,7 @@ The JWS payload of the request object is represented below:
}
],
"redirect_uri":"eudiw://start.wallet.example.org",
"client_assertion_type":"urn:ietf:params:oauth:client-assertion-type:jwt-key-attestation",
"client_assertion_type":"urn:ietf:params:oauth:client-assertion-type:jwt-client-attestation",
}
Expand Down Expand Up @@ -340,7 +340,7 @@ The requests to the PID/(Q)EAA authorization endpoint MUST be HTTP with method P
- It MUST be a signed JWT. The private key corresponding to the public one in the ``cnf`` parameter inside the Wallet Instance Attestation MUST be used for signing the request object.
- `OpenID Connect Core. Section 6 <https://openid.net/specs/openid-connect-core-1_0.html#JWTRequests>`_
* - **client_assertion_type**
- It MUST be set to ``urn:ietf:params:oauth:client-assertion-type:jwt-key-attestation``.
- It MUST be set to ``urn:ietf:params:oauth:client-assertion-type:jwt-client-attestation``.
- `Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants <https://www.rfc-editor.org/rfc/rfc7521>`_
* - **client_assertion**
- It MUST be the Wallet Instance Attestation signed JWT.
Expand Down
5 changes: 3 additions & 2 deletions docs/en/wallet-solution.rst
Original file line number Diff line number Diff line change
Expand Up @@ -157,7 +157,8 @@ Payload `wallet_provider`
+---------------------------------------------+---------------------------------------------------------------------+
| grant_types_supported | The types of grants supported by |
| | the endpoint token. It MUST be set to |
| | ``urn:ietf:params:oauth:client-assertion-type:jwt-key-attestation`` |
| | ``urn:ietf:params:oauth:client-assertion-type: |
| | jwt-client-attestation`` |
+---------------------------------------------+---------------------------------------------------------------------+
| token_endpoint_auth_methods_suppor | Supported authentication method for |
| ted | the endpoint token. |
Expand Down Expand Up @@ -230,7 +231,7 @@ Below a non-normative example of the Entity Configuration.
"https://wallet-provider.example.org/LoA/high"
],
"grant_types_supported": [
"urn:ietf:params:oauth:client-assertion-type:jwt-key-attestation"
"urn:ietf:params:oauth:client-assertion-type:jwt-client-attestation"
],
"token_endpoint_auth_methods_supported": [
"private_key_jwt"
Expand Down

0 comments on commit d7a7f59

Please sign in to comment.