How do you disable headers on a redirect to an outbound API?

[Timothy Onyskin]

I am trying to integrate with TalkDesk so I can pull report data from TalkDesk into a custom table in ServiceNow so that we can report against everything on one dashboard. When I try an API to TalkDesk to create a report, it works fine. When I then try to pull down the report, it complains about using too many authentication methods at one time. In talking with TalkDesk, it seems that this issue is directly related to the headers that are being passed on in the forward to the S3 bucket. The authorization header is being carried over when it forwards to the S3 bucket which then causes this error. TalkDesk recommended I log a ticket with ServiceNow to see if there is an option to disable the authorization header from being carried over on the forward/redirect, so that the request can go through without error. Trying the forum first to see if I can get a quick, but correct, answer.

[Tony Chatfield1]

Hi, to be honest i have never heard of integration 'forwarding' as a solution.
If talkdesk is receiving and authenticating your integration message and then I would think it would be talkdesk who needs to ensure that they properly manage\drop your SNC-talkdesk authentication credentials when they communicate with their target platform - if they are forwarding your talkdesk authentication to another platform then I would think that this was a security issue that they need to address ASAP as they should not pass these authentication details to anyone.

Can you use rest to query S3 directly?

[Timothy Onyski1]

Thank you for your response.  I do not have access to the S3 directly.  It seems it authenticates internally from TalkDesk.  I too believe it is a TalkDesk issue, but they wanted me to log a ticket with ServiceNow since "it works with PostMan".  

[Tony Chatfield1]

Hi, can you get TalkDesk to provide details of the Postman solution\configuration, as first step would be to reproduce and confirm that their working 'solution' is actually via TalkDesk 'forwarding' and not simply them testing directly to S3. This might also help you identify differences in payload.

[Michael Searle]

I wanted to give you a thumbs up just for mentioning integration/connection to Talkdesk. I've been working through it also. I don't have the same issues but it hasn't been a smooth integration. I've made many requests to Talkdesk for support and I'm still working with them to resolve issues.