Hi Joe,
Yes, Rampart supports WS-SecureConversation specification. Please refer to
the Sample-04 of the Rampart binary distribution[1].
Thanks,
Thilina
[1] - http://axis.apache.org/axis2/java/rampart/download.html
Thilina Mahesh Buddhika
http://blog.thilinamb.com
On Thu, Jan 13, 2011 at 1:42
[
https://issues.apache.org/jira/browse/AXIS2-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981130#action_12981130
]
Amila Chinthaka Suriarachchi commented on AXIS2-4705:
-
have you tried w
Hello,
The WS-SecureConversation standard
at
http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512/ws-secureconversation-1.3-os.html
mentions
the following as a way to create a security context token in Section 3:
Security context token created by one of the communicating parties and
[
https://issues.apache.org/jira/browse/AXIS2-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980746#action_12980746
]
Andrew Monastyrev commented on AXIS2-4705:
--
I have same problem with IBM WAS 6.1 a
[
https://issues.apache.org/jira/browse/AXIS2-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Katherine Sanders updated AXIS2-4922:
-
Attachment: AXIS2-4922.patch
The attached patch fixes the problems by making the followin
JAX-WS 2.2 CTS failures in WS-A metadata action code
Key: AXIS2-4922
URL: https://issues.apache.org/jira/browse/AXIS2-4922
Project: Axis2
Issue Type: Bug
Components: Addressing
[
https://issues.apache.org/jira/browse/AXIS2-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruwan Linton resolved AXIS2-4911.
-
Resolution: Fixed
The landing page is live with all the modifications proposed in the JIRA,
than
