Support for token authentication

A SIGNON to C:D Server from PEM via REST API is succesful if using these headers (the value of X-XSRF is fixed and documented on KC, Authorization is Userid/Password in base 64)

Content-Type=application/JSON; charset=iso-8859-1
X-XSRF-TOKEN=Y2hlY2tpdA==
Authorization=Basic ZG5pY2hlOnN0ZXJsaW5n

PEM is receiving then only the body as an example:

[ {
"messageCode" : 200,
"message" : "Signon is successful",
"version" : "6.1.0.0",
"nodeName" : "CDUNIX61"
} ]

The header is not captured, but we need these values like:

XSRF-TOKEN=e00a9b95-a63b-4e32-9f8a-383299e18399

Authorization : oTqJSyTijkZFyoG4iONdpLeX6n8SSZtegbJVusJSxlPShEEcsibA...

fur subsequent REST API Calls to the C:D Server otherwise we get an error.

This can be verified and tested from Postman or other utilities.

Regards

For full Connect:Direct support tokenization will not be enough. You will need to enable as well numbers in json documents instead of only text. Following an example:

This is how the C:D signon json should look like:

{"ipAddress":"127.0.0.1","port":1363,"protocol":"tcpip"}

In PEM you can do this if port number is hard coded. Anyway if you gathered the port number in the PEM activity at some point in time and now want to reuse the number PEM can only generate the number as text. See following the example:

{"ipAddress":"127.0.0.1","port":"1363","protocol":"tcpip"}

Stating the port as text instead of number fails the C:D signon.

PEMs missing support for number stating in json documents effects not only the C:D signon but as well other C:D APIs where number are needed instead of text.

Just to make it clear. PEM prevents saving API calls like this:

{"ipAddress":"127.0.0.1","port":${/Parameters/ActivityContext/Task[@Name="GetPandSnodeInfo"]/Dialog[@Name="GetCDPnodeInfo"]/Response/ObjectNode/apiport/text()},"protocol":"tcpip"}

You can only save it as follows which is by stating a number as text in the json document:

{"ipAddress":"127.0.0.1","port":"${/Parameters/ActivityContext/Task[@Name="GetPandSnodeInfo"]/Dialog[@Name="GetCDPnodeInfo"]/Response/ObjectNode/apiport/text()}","protocol":"tcpip"}

Please consider as well to provide:

• an out of the box activity for SSP and C:D use cases for PEM and PP
• enhance the partner repository  and modify the SSP and C:D configurations.