We have a system that calls a Pega REST Service passing in JSON constructs. The call fails with Inbound data mapping failed. Included in the stack trace is the following message: Attempting to map data to property .MyProperty with unsupported mode: Unknown. (Note: It is failing before getting to the activity that is to handle the request).
Using logging (HttpService), I have captured the JSON payload that is received. I take this same payload and using the REST Service simulator (Actions->Run), Pega is able to successfully parse the JSON. The only difference between the two is the Requestor Context of the REST Service simulator states "Use current requestor context". If there was an authentication/authorization failure, I would expect to see an authentication error and not a mapping error.
[edit update] In case it helps, the first stack lines after Attempting to map data to property .MyProperty with unsupported mode: Unknown.
Simulator will work it's won't make actual connection to REST Service, from the error I can see response is coming as expected so could you please assign the Response to .pyNote property and check the response string.
Posted: 5 years ago
Posted: 6 Jul 2017 10:09 EDT
Rob Jago (Rob_Jago)
The stack trace and response indicate that the activity (triggered by the REST service) is not being executed so I have no control over the mapping. In terms of the mapping of the .pyNote property, which class is that from? (or is it @baseclass.
Investigation so far seems to indicate the authentication part. The Service Package is defined to enforce authentication. When authentication is disabled (unchecked), the request/response works as expected. What I find intriguing is why would an authentication failure still result in an attempt to map inbound data? perhaps it's more of an authorization error than a authentication error. For authentication, we are using Kerberos to protect the server / URL. And, I am starting to believe that the Kerberos token may have expired -- so I am looking into that now.