[SWS-723] Wss4jSecurityInterceptor design Created: 04/Aug/11 Updated: 04/May/12 Resolved: 17/Oct/11
|Project:||Spring Web Services|
|Reporter:||Pavel Král||Assignee:||Arjen Poutsma|
|Remaining Estimate:||Not Specified|
|Original Estimate:||Not Specified|
Wss4jSecurityInterceptor implementation has design restriction making it practically imposible to extend. While working on Kerberos extension in Wss4j, I have to add new properties to configure ServicePrincipalName etc. I suggest to:
|Comment by Kyle Cronin [ 18/Aug/11 ]|
There is no way to get access to RequestData through any other means and therefore forced to use the default WSSConfig. Changing the scope of initializeRequestData would allow users to inject custom WSSconfig into the RequestData.
Attaching a patch where initializeRequestData is protected along with an additional enhancement to configure the WSSConfig for both the WSSecurityEngine and RequestData
|Comment by Pavel Král [ 01/Sep/11 ]|
Seems to be OK, will that patch be applied to the trunk ?
|Comment by Arjen Poutsma [ 17/Oct/11 ]|
Patch applied, thanks!
|Comment by Arjen Poutsma [ 04/May/12 ]|
Closing old issues