- changed status to open
Messages - 4.2 JWK and X509 format support
Issue #633
resolved
The spec does not specify whether JWK or X509 certificates must be supported so there may be interoperability problems with asymmetric signature verification and encryption due lack of common support by the server and client.
Comments (6)
-
-
-
assigned issue to
Michael Jones
We will be discussing this at the face-to-face meeting on October 22, 2012
-
assigned issue to
-
As decided at the 22-Oct-12 working group meeting at Google, OPs must support X.509 certificates.
-
The remaining open issue is whether to define how to support X.509 bare keys (or X.509 RFC 5280 SubjectPublicKeyInfo values) or whether to just require the use of JWK if bare keys are needed.
-
The identified issue has been resolved in favor of X.509.
Whether to support RFC 5280 SubjectPublicKeyInfo values is a separate issue.
-
- changed status to resolved
Fixed
#633- Messages - 4.2 JWK and X509 format support→ <<cset ee690ec3efc4>>
- Log in to comment
We will require publishing and understanding JWK format, with X.509 being optional.