Adobe Campaign SOAP call

[subhajit9830660]

Hi All,

We are facing one issue while calling SOAP methods for our on-premise instance.

The methods in xtk:session (e.g. logon,GetUserInfo) are working fine and we are getting proper response back. However, we are getting "XTK-170019 Access denied" error whenever we call any OOTB (e.g. postEvent in xtk:workflow) or custom methods.

We are using admin credentials for this.

Has anyone faced any similar issue?

Thanks,

Subhajit

[davidk84090111]

Hi Subhajit,

Did you add the header (session token and security token) in your call. Since v6.1  you need to add them or enable the allowUserPassword in the security zones.

Thanks

David

[subhajit9830660]

Hi David,

We are using SOAP UI and passing the session token in the SOAP body. Below is the example of the post event call.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:xtk:workflow">

  <soapenv:Header/>

  <soapenv:Body>

      <urn:PostEvent>

        <urn:sessiontoken>___80719D33-3B50-4696-AEE2-DEE3F8E70671</urn:sessiontoken>

        <urn:strWorkflowId>WKF240</urn:strWorkflowId>

        <urn:strActivity>signal</urn:strActivity>

        <urn:strTransition></urn:strTransition>

        <urn:elemParameters>

            <!--You may enter ANY elements at this point-->

        </urn:elemParameters>

        <urn:bComplete></urn:bComplete>

      </urn:PostEvent>

  </soapenv:Body>

</soapenv:Envelope>

Thanks,

Subhajit

[subhajit9830660]

Hi David,

We are using SOAP UI and passing the session token in the SOAP body. Below is the example of the post event call.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:xtk:workflow">

  <soapenv:Header/>

  <soapenv:Body>

      <urn:PostEvent>

        <urn:sessiontoken>___80719D33-3B50-4696-AEE2-DEE3F8E70671</urn:sessiontoken>

        <urn:strWorkflowId>WKF240</urn:strWorkflowId>

        <urn:strActivity>signal</urn:strActivity>

        <urn:strTransition></urn:strTransition>

        <urn:elemParameters>

            <!--You may enter ANY elements at this point-->

        </urn:elemParameters>

        <urn:bComplete></urn:bComplete>

      </urn:PostEvent>

  </soapenv:Body>

</soapenv:Envelope>

Thanks,

Subhajit

[subhajit9830660 · Accepted solution]

Hi David,

We have resolved the issue. The sessionTokenOnly value was set to false in the serverConf.

Thanks,

Subhajit

[davidk84090111]

Ok great

below are definition of option you can enable/disable in the security zones.

• allowDebug: enables a webApp to be executed in "debug" mode
• allowEmptyPassword: authorizes a connection to an instance without a password
• allowHTTP: a session can be created without using the HTTPS protocol
• allowUserPassword: the session token can have the following form: "<login>/<password>
• sessionTokenOnly: the security token is not required in the connection URL
• showErrors: errors on the server side are forwarded and displayed

Thanks

David