You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Rich Newcomb (JIRA)" <ji...@apache.org> on 2010/07/28 04:57:16 UTC

[jira] Created: (CXF-2914) Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client

Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client
-------------------------------------------------------------------------------------------------

                 Key: CXF-2914
                 URL: https://issues.apache.org/jira/browse/CXF-2914
             Project: CXF
          Issue Type: Bug
          Components: WS-* Components
    Affects Versions: 2.3, 2.2.10
            Reporter: Rich Newcomb


The digest algorithm "http://www.w3.org/2000/09/xmldsig#sha1" is used in digital signatures from clients configured via WS-SecurityPolicy even when an AlgorithmSuite is defined within the policy that should resolve to a different digest algorithm.  For example, the following AlgorithmSuite policy should result in the digest algorithm of "http://www.w3.org/2001/04/xmlenc#sha256" (per the WS-SecurityPolicy specification):

<sp:AlgorithmSuite>
    <wsp:Policy>
        <sp:Basic256Sha256 />
    </wsp:Policy>
</sp:AlgorithmSuite>

The correct digest algorithm is determined by the AlgorithmSuite in the Binding; however, the algorithm information is not propagated to the WSSecSignature object that creates the signature.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (CXF-2914) Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client

Posted by "David Valeri (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Valeri resolved CXF-2914.
-------------------------------

    Resolution: Fixed

> Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client
> -------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2914
>                 URL: https://issues.apache.org/jira/browse/CXF-2914
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.3, 2.2.10
>            Reporter: Rich Newcomb
>            Assignee: David Valeri
>             Fix For: 2.3, 2.2.10
>
>         Attachments: cxf-2914-trunk.patch
>
>
> The digest algorithm "http://www.w3.org/2000/09/xmldsig#sha1" is used in digital signatures from clients configured via WS-SecurityPolicy even when an AlgorithmSuite is defined within the policy that should resolve to a different digest algorithm.  For example, the following AlgorithmSuite policy should result in the digest algorithm of "http://www.w3.org/2001/04/xmlenc#sha256" (per the WS-SecurityPolicy specification):
> <sp:AlgorithmSuite>
>     <wsp:Policy>
>         <sp:Basic256Sha256 />
>     </wsp:Policy>
> </sp:AlgorithmSuite>
> The correct digest algorithm is determined by the AlgorithmSuite in the Binding; however, the algorithm information is not propagated to the WSSecSignature object that creates the signature.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CXF-2914) Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client

Posted by "David Valeri (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CXF-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893664#action_12893664 ] 

David Valeri commented on CXF-2914:
-----------------------------------

Patch applied thanks to Rich.

> Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client
> -------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2914
>                 URL: https://issues.apache.org/jira/browse/CXF-2914
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.3, 2.2.10
>            Reporter: Rich Newcomb
>            Assignee: David Valeri
>             Fix For: 2.3, 2.2.10
>
>         Attachments: cxf-2914-trunk.patch
>
>
> The digest algorithm "http://www.w3.org/2000/09/xmldsig#sha1" is used in digital signatures from clients configured via WS-SecurityPolicy even when an AlgorithmSuite is defined within the policy that should resolve to a different digest algorithm.  For example, the following AlgorithmSuite policy should result in the digest algorithm of "http://www.w3.org/2001/04/xmlenc#sha256" (per the WS-SecurityPolicy specification):
> <sp:AlgorithmSuite>
>     <wsp:Policy>
>         <sp:Basic256Sha256 />
>     </wsp:Policy>
> </sp:AlgorithmSuite>
> The correct digest algorithm is determined by the AlgorithmSuite in the Binding; however, the algorithm information is not propagated to the WSSecSignature object that creates the signature.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CXF-2914) Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client

Posted by "David Valeri (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Valeri updated CXF-2914:
------------------------------

    Fix Version/s: 2.3
                   2.2.10

> Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client
> -------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2914
>                 URL: https://issues.apache.org/jira/browse/CXF-2914
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.3, 2.2.10
>            Reporter: Rich Newcomb
>            Assignee: David Valeri
>             Fix For: 2.3, 2.2.10
>
>         Attachments: CXF-2914-trunk.patch
>
>
> The digest algorithm "http://www.w3.org/2000/09/xmldsig#sha1" is used in digital signatures from clients configured via WS-SecurityPolicy even when an AlgorithmSuite is defined within the policy that should resolve to a different digest algorithm.  For example, the following AlgorithmSuite policy should result in the digest algorithm of "http://www.w3.org/2001/04/xmlenc#sha256" (per the WS-SecurityPolicy specification):
> <sp:AlgorithmSuite>
>     <wsp:Policy>
>         <sp:Basic256Sha256 />
>     </wsp:Policy>
> </sp:AlgorithmSuite>
> The correct digest algorithm is determined by the AlgorithmSuite in the Binding; however, the algorithm information is not propagated to the WSSecSignature object that creates the signature.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CXF-2914) Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client

Posted by "Rich Newcomb (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rich Newcomb updated CXF-2914:
------------------------------

    Attachment:     (was: CXF-2914-trunk.patch)

> Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client
> -------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2914
>                 URL: https://issues.apache.org/jira/browse/CXF-2914
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.3, 2.2.10
>            Reporter: Rich Newcomb
>            Assignee: David Valeri
>             Fix For: 2.3, 2.2.10
>
>
> The digest algorithm "http://www.w3.org/2000/09/xmldsig#sha1" is used in digital signatures from clients configured via WS-SecurityPolicy even when an AlgorithmSuite is defined within the policy that should resolve to a different digest algorithm.  For example, the following AlgorithmSuite policy should result in the digest algorithm of "http://www.w3.org/2001/04/xmlenc#sha256" (per the WS-SecurityPolicy specification):
> <sp:AlgorithmSuite>
>     <wsp:Policy>
>         <sp:Basic256Sha256 />
>     </wsp:Policy>
> </sp:AlgorithmSuite>
> The correct digest algorithm is determined by the AlgorithmSuite in the Binding; however, the algorithm information is not propagated to the WSSecSignature object that creates the signature.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (CXF-2914) Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client

Posted by "David Valeri (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Valeri reassigned CXF-2914:
---------------------------------

    Assignee: David Valeri

> Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client
> -------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2914
>                 URL: https://issues.apache.org/jira/browse/CXF-2914
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.3, 2.2.10
>            Reporter: Rich Newcomb
>            Assignee: David Valeri
>         Attachments: CXF-2914-trunk.patch
>
>
> The digest algorithm "http://www.w3.org/2000/09/xmldsig#sha1" is used in digital signatures from clients configured via WS-SecurityPolicy even when an AlgorithmSuite is defined within the policy that should resolve to a different digest algorithm.  For example, the following AlgorithmSuite policy should result in the digest algorithm of "http://www.w3.org/2001/04/xmlenc#sha256" (per the WS-SecurityPolicy specification):
> <sp:AlgorithmSuite>
>     <wsp:Policy>
>         <sp:Basic256Sha256 />
>     </wsp:Policy>
> </sp:AlgorithmSuite>
> The correct digest algorithm is determined by the AlgorithmSuite in the Binding; however, the algorithm information is not propagated to the WSSecSignature object that creates the signature.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CXF-2914) Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client

Posted by "Rich Newcomb (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rich Newcomb updated CXF-2914:
------------------------------

    Attachment: CXF-2914-trunk.patch

The attached patch seems to resolve the issue.  Unit tests to follow.

> Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client
> -------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2914
>                 URL: https://issues.apache.org/jira/browse/CXF-2914
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.3, 2.2.10
>            Reporter: Rich Newcomb
>         Attachments: CXF-2914-trunk.patch
>
>
> The digest algorithm "http://www.w3.org/2000/09/xmldsig#sha1" is used in digital signatures from clients configured via WS-SecurityPolicy even when an AlgorithmSuite is defined within the policy that should resolve to a different digest algorithm.  For example, the following AlgorithmSuite policy should result in the digest algorithm of "http://www.w3.org/2001/04/xmlenc#sha256" (per the WS-SecurityPolicy specification):
> <sp:AlgorithmSuite>
>     <wsp:Policy>
>         <sp:Basic256Sha256 />
>     </wsp:Policy>
> </sp:AlgorithmSuite>
> The correct digest algorithm is determined by the AlgorithmSuite in the Binding; however, the algorithm information is not propagated to the WSSecSignature object that creates the signature.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CXF-2914) Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client

Posted by "Rich Newcomb (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rich Newcomb updated CXF-2914:
------------------------------

    Attachment: cxf-2914-trunk.patch

Attached an updated patch that includes supporting unit tests.

> Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client
> -------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2914
>                 URL: https://issues.apache.org/jira/browse/CXF-2914
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.3, 2.2.10
>            Reporter: Rich Newcomb
>            Assignee: David Valeri
>             Fix For: 2.3, 2.2.10
>
>         Attachments: cxf-2914-trunk.patch
>
>
> The digest algorithm "http://www.w3.org/2000/09/xmldsig#sha1" is used in digital signatures from clients configured via WS-SecurityPolicy even when an AlgorithmSuite is defined within the policy that should resolve to a different digest algorithm.  For example, the following AlgorithmSuite policy should result in the digest algorithm of "http://www.w3.org/2001/04/xmlenc#sha256" (per the WS-SecurityPolicy specification):
> <sp:AlgorithmSuite>
>     <wsp:Policy>
>         <sp:Basic256Sha256 />
>     </wsp:Policy>
> </sp:AlgorithmSuite>
> The correct digest algorithm is determined by the AlgorithmSuite in the Binding; however, the algorithm information is not propagated to the WSSecSignature object that creates the signature.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.