remove `c_nonce` from the token endpoint response#381

Merged

jogu merged 12 commits intomainfrom remove-c_nonce-from-the-token-endpoint-response

Oct 8, 2024

+50-19

Commits on Aug 27, 2024

remove c_nonce and c_nonce_expires_in from the token endpoint response to fix #39
bc-pi
committed

Commits on Sep 4, 2024

added a Nonce Endpoint where a Client can acquire a fresh c_nonce value without the overhead of a full Credential Request
bc-pi
committed

Commits on Sep 6, 2024

mandate nonce endpoint if the issuer requires the use of c_nonce
bc-pi
committed

Commits on Sep 10, 2024

improve readability via Sakurann

bc-pi
and
Sakurann
authored

Commits on Sep 16, 2024

make nonce response uncacheable
bc-pi
committed

Commits on Sep 18, 2024

c_nonce_expires_in is just a hint and not more than a hint
bc-pi
authored

Commits on Sep 20, 2024

paul fix an a too far

bc-pi
and
paulbastian
authored

Commits on Sep 24, 2024

big MUST to little can
bc-pi
committed

Commits on Sep 25, 2024

big C

bc-pi
and
peppelinux
authored

Commits on Sep 30, 2024

Removed the HTTP method specificity from the Nonce Request text and change the example from GET to POST
bc-pi
committed

Commits on Oct 1, 2024

HTTP is as HTTP does
bc-pi
authored

Commits on Oct 8, 2024

joseph's suggested text for "making the use of the nonce_endpoint by the client mandatory if it's present and a nonce is required"

bc-pi
and
jogu
authored