- changed status to resolved
Change keys in Standard to use JWK representation
Please change all the key representations in Standard to use JWK format rather than hex.
Also, please update the request token values that are encoded in the examples to be formatted in the way that the ones in the specs are (less indentation). If you use the text from the current specs, please remove two leading spaces from each line before encoding the example. (There are two leading spaces at the start of all lines for formatting purposes.)
Comments (5)
-
-
reporter - changed status to open
Several issues with the new text need to be addressed.
On lines 966, 1007, 1073, and 1146 you changed "sub" to "user_id".
On line 971 you used a 256 bit at_hash value, rather than the left 128 bits of the hash value.
Also, while these aren't new bugs, I'm hoping you can fix them too while you're fixing the above one...
On line 1078, the at_hash value is 256 bits, rather than 128 bits.
On lines 1012, 1079, and 1154, the c_hash value is 256 bits, rather than 128 bits.
Thanks, -- Mike
-
- changed status to resolved
fixes
#707: Change keys in Standard to use JWK representation→ <<cset 45e3d7f0a29b>>
-
addresses
#707: Change keys in Standard to use JWK representation, updated birthdate example→ <<cset 3ee9ab457383>>
-
- changed milestone to Implementer's Draft
- Log in to comment
fixes
#707: Change keys in Standard to use JWK representation→ <<cset ed71fde2edea>>