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 Zhemzhitsky (JIRA)" <ji...@apache.org> on 2011/08/19 08:27:27 UTC

[jira] [Issue Comment Edited] (CXF-3706) It's impossible to use wss4j.action.map and wss4j.processor.map with WS-Policy

    [ https://issues.apache.org/jira/browse/CXF-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087568#comment-13087568 ] 

Sergey Zhemzhitsky edited comment on CXF-3706 at 8/19/11 6:26 AM:
------------------------------------------------------------------

Hi Colm,

I would like to use custom algorithms to sign and encrypt the messages.
In WSS4JInInterceptor I was able to do it defining custom processors and actions by means of wss4j.action.map and wss4j.processor.map properties like this

{code}
<entry key="wss4j.processor.map">
    <map key-type="javax.xml.namespace.QName" value-type="java.lang.Class">
        <entry>
            <key>
                <bean class="javax.xml.namespace.QName">
                    <constructor-arg value="http://www.w3.org/2001/04/xmlenc#" />
                    <constructor-arg value="EncryptedKey" />
                </bean>
            </key>
            <value>MyCustomEncryptedKeyProcessor</value>
        </entry>
        <entry>
            <key>
                <bean class="javax.xml.namespace.QName">
                    <constructor-arg value="http://www.w3.org/2000/09/xmldsig#" />
                    <constructor-arg value="Signature" />
                </bean>
            </key>
            <value>MyCustomSignatureProcessor</value>
        </entry>
    </map>
</entry>
{code}
{code}
<entry key="wss4j.action.map">
    <map key-type="java.lang.Integer" value-type="java.lang.Class">
        <entry>
            <key>
                <util:constant static-field="org.apache.ws.security.WSConstants.SIGN" />
            </key>
            <value>MySignatureAction</value>
        </entry>
    </map>
</entry>
{code}

If such changes are hardly possible to apply in case of WS-POlicy, please close this improvement.

      was (Author: szhemzhitsky):
    Hi Colm,

I would like to use custom algorithms to sign and encrypt the messages.
In WSS4JInInterceptor I was able to do it defining custom processors and actions by means of wss4j.action.map and wss4j.processor.map properties like this

{code}
                <entry key="wss4j.processor.map">
                    <map key-type="javax.xml.namespace.QName" value-type="java.lang.Class">
                        <entry>
                            <key>
                                <bean class="javax.xml.namespace.QName">
                                    <constructor-arg value="http://www.w3.org/2001/04/xmlenc#"/>
                                    <constructor-arg value="EncryptedKey"/>
                                </bean>
                            </key>
                            <value>MyCustomEncryptedKeyProcessor</value>
                        </entry>
                        <entry>
                            <key>
                                <bean class="javax.xml.namespace.QName">
                                    <constructor-arg value="http://www.w3.org/2000/09/xmldsig#"/>
                                    <constructor-arg value="Signature"/>
                                </bean>
                            </key>
                            <value>MyCustomSignatureProcessor</value>
                        </entry>
                    </map>
                </entry>
{code}
{code}
                <entry key="wss4j.action.map">
                    <map key-type="java.lang.Integer" value-type="java.lang.Class">

                        <entry>
                            <key>
                                <util:constant static-field="org.apache.ws.security.WSConstants.SIGN"/>
                            </key>
                            <value>MyCustomSignatureAction</value>
                        </entry>
                    </map>
                </entry>
{code}

If such changes are hardly possible to apply in case of WS-POlicy, please close this improvement.
  
> It's impossible to use wss4j.action.map and wss4j.processor.map with WS-Policy
> ------------------------------------------------------------------------------
>
>                 Key: CXF-3706
>                 URL: https://issues.apache.org/jira/browse/CXF-3706
>             Project: CXF
>          Issue Type: Improvement
>          Components: WS-* Components
>    Affects Versions: 2.4.1
>            Reporter: Sergey Zhemzhitsky
>              Labels: ws-security
>
> Sometimes it is necessary to customize a behavior of wss4j.
> It's possible with org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor and org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor by means of wss4j.action.map and wss4j.processor.map properties.
> However it's hardly possible to do with org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JInInterceptor and org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira