Getting response code 401for rest connector although password is correct
Sometime I am getting response code of rest connector 401 in production although password is correct.
I am using Auth profile for authentication and Preemptive authentication check box is checked
STATUS="FATAL" ; RESPONSE_CODE="401"; EVENT_MESSAGE="Publish Event API has returned an error. STATUS_VALUE=Fail:InternalReason ; RESPONSE_MESSAGE= ERROR_MESSAGE= com.pega.pegarules.pub.services.InboundMappingException: Error mapping incoming response to .response_POST: com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')
Could you please increase logging level for that specific class in Designer Studio and then check logs again?
Could you also enable logging on Load balancer or if this is a single server on the network device and analyze network traffic? If this is an intermittent problem it can be an issue with the network, and from time to time server receives broken json or html.
Posted: 3 years ago
Posted: 6 Jul 2018 8:59 EDT
John Pritchard-Williams (JOHNPW_GCS)
Client Support Team Lead
I agree with the post above - you need to get some more logging (and possibly 'sniffing') going on here to double-check.
Here's a theory though:
1. You have a Load Balancer - and/or a Proxy and/or you are using Single Sign On ....
2. The Load Balancer (or Proxy....) is intercepting your outgoing request; and for whatever reason has decided you are NOT authenticated. (Hence the 401).
3. The apparent PARSE message; it may be that this Load Balancer (Proxy whatever) is talking back not in JSON, but in HTML (or XML)....
Regardless if my theory above is correct or incorrect; I still think it would be correct for you to intercept that HTTP 401 message - and payload - from the server for the next clue as to what could be going wrong here.