[
https://issues.apache.org/jira/browse/RAMPART-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya resolved RAMPART-219.
------------------------------------------------
Resolution: Fixed
Applied the patch in revision 752370 and tested with proposed wss4j 1.5.6 in
the staged repo in http://people.apache.org/~coheigea/stage/wss4j/1.5.6/maven/.
thanks,
Nandana
> Get Rampart working with WSS4J 1.5.6(-SNAPSHOT)
> -----------------------------------------------
>
> Key: RAMPART-219
> URL: https://issues.apache.org/jira/browse/RAMPART-219
> Project: Rampart
> Issue Type: Task
> Reporter: Colm O hEigeartaigh
> Assignee: Nandana Mihindukulasooriya
> Attachments: rampart.patch
>
>
> WSS4J 1.5.6 is about to be released. There are two issues with the Rampart
> pom:
> 1) The dependency on WSS4J is "SNAPSHOT". This is the old version which
> hasn't been updated since last December:
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/ws/security/wss4j/SNAPSHOT/
> The current WSS4J (snapshot) version is 1.5.6-SNAPSHOT:
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/ws/security/wss4j/1.5.6-SNAPSHOT/
> 2) There's a dependency on opensaml 1.1:
> <dependency>
> <groupId>opensaml</groupId>
> <artifactId>opensaml</artifactId>
> <version>1.1</version>
> </dependency>
> This is coming from the ws.zones repo. You might want to change the groupId
> to "org.opensaml" so it gets pulled in from the central maven repo instead.
> In addition, some changes are needed to Rampart source relating to handling
> absolute URI's rather than just relative ones. These changes are needed due
> to a change in WSS4J's DerivedKeyProcessor to be able to handle absolute URIs:
> http://svn.apache.org/viewvc/webservices/wss4j/trunk/src/org/apache/ws/security/processor/DerivedKeyTokenProcessor.java?r1=727629&r2=747554
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
