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 2016/02/29 14:13:18 UTC
[jira] [Updated] (CXF-6808) Update JWS/JWE utils to load named
properties
[ https://issues.apache.org/jira/browse/CXF-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin updated CXF-6808:
----------------------------------
Description:
Right now JOSE utils load JWE/JWS properties identified by CXF message contextual properties such as RSSES_SIGNATURE(IN/OUT)_PROPS, etc.
In a complex system such as OIDC/etc it can become limiting, for example, the same endpoint may need to use different output/input signature/encryption tasks so with using a single properties file it may be difficult to identify which algorithm applies to which operation, etc...
Supporting loading named properties files will make it easier, with the system knowing in advance which properties file is needed for which operation
was:
Right now JOSE utils load JWE/JWS properties identified by CXF message contextual properties such as RSSES_SIGNATURE(IN/OUT)_PROPS, etc.
In a complex system such as OIDC/etc it can become limiting, for example, the same endpoint may need to use different output/input signature/encryption tasks so with using a single properties file it may be difficult to identify which algorithm apply to which operation, etc...
Supporting loading named properties files will make it easier, with the system knowing in advance which properties file is needed for which operation
> Update JWS/JWE utils to load named properties
> ---------------------------------------------
>
> Key: CXF-6808
> URL: https://issues.apache.org/jira/browse/CXF-6808
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS, JAX-RS Security
> Reporter: Sergey Beryozkin
> Priority: Minor
> Fix For: 3.2.0
>
>
> Right now JOSE utils load JWE/JWS properties identified by CXF message contextual properties such as RSSES_SIGNATURE(IN/OUT)_PROPS, etc.
> In a complex system such as OIDC/etc it can become limiting, for example, the same endpoint may need to use different output/input signature/encryption tasks so with using a single properties file it may be difficult to identify which algorithm applies to which operation, etc...
> Supporting loading named properties files will make it easier, with the system knowing in advance which properties file is needed for which operation
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)