[
https://issues.apache.org/jira/browse/GERONIMO-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Mehta updated GERONIMO-5366:
----------------------------------
Attachment: WebServiceSecurity_ClientSide.txt
Added the ASF license header.
> To enable the ws-security support in Axis2/Tomcat JAX-WS provider in Apache
> Geronimo
> ------------------------------------------------------------------------------------
>
> Key: GERONIMO-5366
> URL: https://issues.apache.org/jira/browse/GERONIMO-5366
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: webservices
> Environment: Apache Geronimo, Apache Axis2, Apache Tomcat,
> WS-Security, Web Services, Java, Linux
> Reporter: Rahul Mehta
> Priority: Minor
> Attachments: RampartModule.txt, WebServiceSecurity_ClientSide.txt
>
>
> Cross reference#GERONIMO-4642
> Hello Devs,
> This JIRA aims to enable the WS-Security support in "Apache Geronimo- in
> Axis2/Tomcat". During my Google summer of code project last year, I worked on
> setting up WS_Security in CXF/Jetty JAX-WS provider in Apache geronimo (plz
> have a look at GERONIMO-4642) and that is still ongoing. This JIRA is
> dedicated to Axis2/Tomcat JAX-WS provider.
> Some appropriate information about how to set up WS-Security is given in JIRA
> GERONIMO-4642.
> For axis2 part, we will first need Rampart module (based on WSS4J) as
> security module. I will first start pulling required rampart modules in the
> apache geronimo and then start with setting the client side out flow
> security. Later I will move to Server side inflow security.
> Look forward to seeing your feedbacks.
> Many Thanks,
> Rahul
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.