The server encountered an unexpected condition which prevented it from fulfilling the request

We are trying to create a call to our internal API using an okta token. The okta token works in other data actions and I believe it is working in this data action. This is calling to get ACH info to pass to our payment app. We validated that the Okta token works fine using postman. We opened a case with support Case #0003519548 and am not getting very far so I wanted to reach out to the community/Forum and see if anyone is able to help or of you have seen this error and how to get through it.

Genesys client error:

The server encountered an unexpected condition which prevented it from fulfilling the request.

REST call for action execute failed. Message: Request to backend service failed. Response from web service: {"details":{"eventId":"69c56f68-752a-482a-836e-02f14a563a5e","exception":null},"httpStatusCode":null,"errorId":"UNEXPECTED","message":"Unable to process the request. Please contact support"} [5f0114d8-709b-4071-9ca0-800afd186175]

The server side of the API is giving this error:

System.ArgumentException: IDX12709: CanReadToken() returned false. JWT is not well formed: 'System.String'.
The token needs to be in JWS or JWE Compact Serialization Format. (JWS): 'EncodedHeader.EndcodedPayload.EncodedSignature'. (JWE): 'EncodedProtectedHeader.EncodedEncryptedKey.EncodedInitializationVector.EncodedCiphertext.EncodedAuthenticationTag'.

You might use a tool like Requestbin and have both Postman and the Genesys Cloud Data Action send the request to Requestbin. You'll then be able to see what is being sent from both and then you can perform a DIFF to see what might be different.

Alternatively you might have you server log out the raw request that is received off of the wire so that you can compare them both from your server instead of having to use a tool like Requestbin.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.