You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2017/06/20 14:15:00 UTC
[jira] [Resolved] (CXF-6728) Review and improve the way EC keys are
handled in JOSE code
[ https://issues.apache.org/jira/browse/CXF-6728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin resolved CXF-6728.
-----------------------------------
Resolution: Fixed
Assignee: Sergey Beryozkin
Fix Version/s: 3.1.12
3.2.0
> Review and improve the way EC keys are handled in JOSE code
> -----------------------------------------------------------
>
> Key: CXF-6728
> URL: https://issues.apache.org/jira/browse/CXF-6728
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS Security
> Reporter: Sergey Beryozkin
> Assignee: Sergey Beryozkin
> Fix For: 3.2.0, 3.1.12
>
>
> The code which decodes/encodes JOSE EC key outputs needs to be reviewed. The current code was meant to be a more optimal version of the code available in Jose4J (which is actually a slightly improved version of the code found in Santuario plus dealing with JOSE specific optimizations). This code needs to be double-checked and if needed reverted to a version closer to the one found in Jose4J.
> Curves: it should be possible to deduce the values from the current EC key as opposed to having users configure them explicitly.
> Next,
> https://tools.ietf.org/html/draft-ietf-jose-cfrg-curves-00
> has just come out, so I guess EC code will need to be updated accordingly.
> I also recall that if EC keys are loaded from JKS then the default algorithm needs be set correctly if EC signature/enc algo is not set, at the moment it is always set to RS256 by default
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)