You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2012/04/30 14:44:51 UTC
[jira] [Created] (CXF-4277) STSClient does not use returned KeyInfo
size when creating a secret key
Colm O hEigeartaigh created CXF-4277:
----------------------------------------
Summary: STSClient does not use returned KeyInfo size when creating a secret key
Key: CXF-4277
URL: https://issues.apache.org/jira/browse/CXF-4277
Project: CXF
Issue Type: Bug
Components: WS-* Components
Affects Versions: 2.6, 2.5.3, 2.4.7
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
Fix For: 2.6.1, 2.5.4, 2.4.8
The STSClient does not use the returned KeyInfo size when creating a secret key. This means that it creates an incorrect secret key in the case where an STS rejects the submitted KeySize, and returns a different KeySize to the client.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4277) STSClient does not use returned
KeyInfo size when creating a secret key
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh resolved CXF-4277.
--------------------------------------
Resolution: Fixed
> STSClient does not use returned KeyInfo size when creating a secret key
> -----------------------------------------------------------------------
>
> Key: CXF-4277
> URL: https://issues.apache.org/jira/browse/CXF-4277
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.4.7, 2.5.3, 2.6
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Fix For: 2.6.1, 2.5.4, 2.4.8
>
>
> The STSClient does not use the returned KeyInfo size when creating a secret key. This means that it creates an incorrect secret key in the case where an STS rejects the submitted KeySize, and returns a different KeySize to the client.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4277) STSClient does not use returned KeyInfo
size when creating a secret key
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-4277:
-----------------------------
Description: The STSClient does not use the returned KeyInfo size when creating a secret key. This means that it creates an incorrect secret key in the case where an STS rejects the submitted KeySize, and returns a different KeySize to the client. (was:
The STSClient does not use the returned KeyInfo size when creating a secret key. This means that it creates an incorrect secret key in the case where an STS rejects the submitted KeySize, and returns a different KeySize to the client.)
Fix Version/s: 2.3.11
> STSClient does not use returned KeyInfo size when creating a secret key
> -----------------------------------------------------------------------
>
> Key: CXF-4277
> URL: https://issues.apache.org/jira/browse/CXF-4277
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.4.7, 2.5.3, 2.6
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Fix For: 2.6.1, 2.5.4, 2.4.8, 2.3.11
>
>
> The STSClient does not use the returned KeyInfo size when creating a secret key. This means that it creates an incorrect secret key in the case where an STS rejects the submitted KeySize, and returns a different KeySize to the client.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira