[SWS-989] Setting up a Wss4jSecurityInterceptor as no security still requires WS-Security header Created: 30/May/17  Updated: 30/Oct/17  Resolved: 10/Jul/17

Status: Closed
Project: Spring Web Services
Component/s: None
Affects Version/s: None
Fix Version/s: 2.4.1

Type: Bug Priority: Minor
Reporter: Jeff Torson Assignee: Greg Turnquist
Resolution: Complete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relate
relates to SWS-1008 Remove NO_SECURITY check in 3.x Closed
Supersede
supersedes SWS-961 WSS4J2 Wss4jSecurityInterceptor -> va... Closed
Pull Request URL: https://github.com/spring-projects/spring-ws/pull/90

 Description   

When trying to use Wss4jSecurityInterceptor from the wss4j2 package, validation is still performed when no security is set. This does not happen from the deprecated one in the wss4j package. We use this as a simple simulator and thus we turned security off. It looks like the real issue is that when calling WSSecurityUtil.decodeAction(), when NO_SECURITY is used, it returns an empty list instead of a list with 0 in it and thus:

if (validationActionsVector.contains(WSConstants.NO_SECURITY)) 

fails in validateMessage() since the list is really empty.


Generated at Sun Dec 17 10:03:45 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.