[
https://issues.apache.org/jira/browse/RAMPART-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910582#comment-13910582
]
Wally Dennis commented on RAMPART-391:
--------------------------------------
This should be higher priority - it is causing an interop issue with Metro,
WSS4J natively provided a mechanism for disabling this check, so Rampart should
as well (or at least look for the WSS4J property and use it to set the
compliance level).
> Add ability to set the wsiBspComplient property in WSSConfig
> ------------------------------------------------------------
>
> Key: RAMPART-391
> URL: https://issues.apache.org/jira/browse/RAMPART-391
> Project: Rampart
> Issue Type: Improvement
> Components: rampart-core
> Affects Versions: 1.6.2
> Reporter: Kristina Petkova
> Priority: Minor
> Labels: bsp-compliance, property
>
> There is this property wsiBspComplient which is set to true by default in the
> WSSConfig class:
> http://people.apache.org/~coheigea/stage/wss4j/1.5.6/site/apidocs/org/apache/ws/security/WSSConfig.html
> You could only change it like this:
> setWsiBSPCompliant(boolean wsiBSPCompliant)
> Set the WS-I Basic Security Profile compliance mode.
> but you cannot set it through rampart. This could be added as functionality.
> It would be also useful if a there is a property in Rampart configuration in
> order the client to use it via the services.xml.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
