I'm running into an issue with my integration, as I have create web data action also I used Custom Oauth and I
defined all the required fields into it and It's working fine, Once I create a new action I have mentioned in its
header the below "Authorization": "${authResponse.token_type} ${authResponse.access_token}", once I'm
trying to do test it showcase to me the below:
Execute: No authentication bearer token specified in authorization header.
REST call for action execute failed. Message: Request to backend service failed. Response from web service: [9c8179a5-2a30-4cf0-b013-89e7c96247b4]
Despite the Fact I have mentioned the type of token as well as token in the header with no use, however I have
walked through previous threads and I have saw that you should add "Transfer-Encoding" into web data action
, Once I add it, its not added in the data action authentication request header
Kindly find the attached for more details
Do you know what kind of encoding you are using? Under Content-Type you could add a Transfer-Encoding header with the value of buffered if the site you are sending to doesn't support chunked encoding which I believe is the default with Genesys.
Kindly note that I have added the following "Transfer-Encoding:buffered" and its still showcase the same error which's
Execute: No authentication bearer token specified in authorization header.
REST call for action execute failed. Message: Request to backend service failed. Response from web service: [ed2fd7ae-2d3e-4f10-8253-91c37a05a39b]
For the action that is failing do you have an "Authorization" header configured? It would commonly look like"Authorization": "${authResponse.token_type} ${authResponse.access_token}",
--Jason
I have mentioned it and its always failed, also I have added the Transfer-Encoding I give it a try and its failed
moreover I have did the test with out the transfer-encoding and its always failed, Kindly find the attached
Are you able to make a successful call to this end point using postman with a valid token? Just to narrow down where the issue is?
Dear @ObsTech
Thank you for your time,
my issue is exactly with bearer token as I'm able to get all authentication details from the authentication request,
but when I'm trying to use this information in the second request I got the following return code"401"
When you run the second request in test mode, are you seeing a reasonable authorization header being set (I think it will hide the characters, but tell you how many characters were in it)
system
May 28, 2023, 5:21pm
9
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
