Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Adobe Campaign SOAP call

Avatar

Avatar
Validate 1
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct Reply

5 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile

Avatar
Validate 1
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct Reply

5 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile
subhajit9830660
Level 3

03-05-2018

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

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct Reply

5 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile

Avatar
Validate 1
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct Reply

5 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile
subhajit9830660
Level 3

03-05-2018

Hi David,

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

Thanks,

Subhajit

Answers (4)

Answers (4)

Avatar

Avatar
Boost 1
Level 2
davidk84090111
Level 2

Likes

2 likes

Total Posts

8 posts

Correct Reply

3 solutions
Top badges earned
Boost 1
Affirm 3
Affirm 1
View profile

Avatar
Boost 1
Level 2
davidk84090111
Level 2

Likes

2 likes

Total Posts

8 posts

Correct Reply

3 solutions
Top badges earned
Boost 1
Affirm 3
Affirm 1
View profile
davidk84090111
Level 2

03-05-2018

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

Avatar

Avatar
Validate 1
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct Reply

5 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile

Avatar
Validate 1
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct Reply

5 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile
subhajit9830660
Level 3

03-05-2018

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

Avatar

Avatar
Validate 1
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct Reply

5 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile

Avatar
Validate 1
Level 3
subhajit9830660
Level 3

Likes

16 likes

Total Posts

33 posts

Correct Reply

5 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile
subhajit9830660
Level 3

03-05-2018

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

Avatar

Avatar
Boost 1
Level 2
davidk84090111
Level 2

Likes

2 likes

Total Posts

8 posts

Correct Reply

3 solutions
Top badges earned
Boost 1
Affirm 3
Affirm 1
View profile

Avatar
Boost 1
Level 2
davidk84090111
Level 2

Likes

2 likes

Total Posts

8 posts

Correct Reply

3 solutions
Top badges earned
Boost 1
Affirm 3
Affirm 1
View profile
davidk84090111
Level 2

03-05-2018

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