JWK Thumbprint (in)compatibility?
cyberphone opened this issue · 1 comments
cyberphone commented
This issue was created based on external input.
In spite of the fact that JCS sorts properties based on UTF-16 values rather than on Unicode code points as specified in https://tools.ietf.org/html/rfc7638, JCS is 100% compatible with all at the time of writing published JWK variants and their thumbprint counterparts.
This is because existing JWKs use ASCII characters for keys and stick to I-JSON for numeric data.
cyberphone commented
Since section 4 of https://tools.ietf.org/html/rfc7638 clearly hints adhering to certain rules for new JWKs which are compatible with JCS, this potential problem can IMO safely be dismissed.