Secuirty error using webServiceClient component

vikceo

• January 18, 2013 00:00

• Answered

Follow

I am trying to call a webservice and see following errors in the log. The authorization policy using Basic I am able to call the same webservice using soapUI by setting the Authentication type to Preemptive. I dont see any such option in WebServiceClient component in cloverETL.

NFO [WEB_SERVICE_CLIENT1_0] - Web Service Client Fault response:
<env:Fault xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>env:Server</faultcode><faultstring>access denied (oracle.wsm.security.WSFunctionPermission http://xmlns.oracle.com/apps/incentiveC ... etDispute1 invoke)</faultstring></env:Fault>
INFO [WEB_SERVICE_CLIENT1_0] - Error occured while executing web service call. Printing request/response details:
INFO [WEB_SERVICE_CLIENT1_0] - Web Service Client request header:
null
INFO [WEB_SERVICE_CLIENT1_0] - Web Service Client request body:
<typ:getDispute1 xmlns:typ="http://xmlns.oracle.com/apps/incentiveCompensation/cn/disputeManagement/model/types/"> <typ:disputeId>123</typ:disputeId></typ:getDispute1>
INFO [WEB_SERVICE_CLIENT1_0] - Web Service Client response:
null
TRACE [WEB_SERVICE_CLIENT1_0] - reset thread runId; runId:0 thread name:WEB_SERVICE_CLIENT1_0
ERROR [WatchDog_0] - Graph execution finished with error
ERROR [WatchDog_0] - Node WEB_SERVICE_CLIENT1 finished with status: ERROR caused by: access denied (oracle.wsm.security.WSFunctionPermission http://xmlns.oracle.com/apps/incentiveC ... etDispute1 invoke)
ERROR [WatchDog_0] - Node WEB_SERVICE_CLIENT1 error details:
org.apache.axis2.AxisFault: access denied (oracle.wsm.security.WSFunctionPermission http://xmlns.oracle.com/apps/incentiveC ... etDispute1 invoke)
at org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:451)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
INFO [WatchDog_0] - [Clover] Post-execute phase finalization: 0

• 

  imriskal

  • May 14, 2013 12:12

  0

  Comment actions Permalink

  Hi, vikceo,
  
  We are sorry but at the moment, WebServiceClient can not be set to support preemptive authentication type. Thank you for your feedback, I have created an issue in our bug tracking system, see https://bug.javlin.eu/browse/CLO-794
  
  One possible workaround could be replacement of WebServiceClient with HTTPConnector. In Additional HTTP headers, set Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==
  For more details, see http://en.wikipedia.org/wiki/Basic_acce ... entication, chapter Protocol - Client side.
  
  Best regards,
• 

  samuelt

  • February 24, 2015 03:45

  0

  Comment actions Permalink

  After version 4.0.3, WebServiceClient seems it still can not be set to preemptive authentication type.
  
  Could someone get this fixed?

Please sign in to leave a comment.