In Apache Axis2/Rampart, while generating wsdl and validating policy, is Ws-security Policy 1.2 assertion <sp:NoPassword/> not handled completely? -
we implementing ws-security policy on our web services following framework/module/specification.
apache axis2 1.6.2
apache rampart 1.6.2
ws-security policy 1.2(namespace:http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702)
we facing following issues while creating/consuming service.
- axis2 wsdl generation logic ignores
<sp:nopassword/>
assertion. after debugging,i realized because of logic in org.apache.ws.secpolicy.model.usernametoken (rampart-policy-1.6.2.jar) expects<sp:wssusernametoken11 />
( or<sp:wssusernametoken10 />
) specified - again when specify that,<sp:nopassword/>
created child element of<sp:wssusernametoken11 />
causing<sp:nopassword/>
ignored on client (consumer) side. - in implementation of
org.apache.rampart.policybasedresultsvalidator/handlesupportingtokens
method - nopassword scenario not considerd ; hence fails saying "org.apache.axis2.axisfault: usernametoken missing in request". - on consumer side, ws security policy 1.2 work, had remove rahas-1.6.2.mar client side rampart repository;there jira ticket - https://issues.apache.org/jira/browse/rampart-371
please suggest if missed here.
Comments
Post a Comment