Hi, we are currently integrating with a Dynamics environment, where we want to pull some data from the system. There is no need for a screen pop, just show some fields to the agents using Scripter.
I have added the Data Action and did a custom authentication, when testing this authentication I get all lights green.
So there is something in the header, but the Data Action says no.
When testing this with Postman, I first use a request to catch the bearerToken, save this as an environment variable. And then do a second request where that environment variable is set in the the Authorization header.
I don't know if it was Dynamics, but there was at least one web service where they would return the token_type with a specific casing, like "bearer" but they would only accept a different casing, like "Bearer". Might check that. I see that you already have Transfer-Encoding set to buffered, which does resolve a lot of weird problems. If you still can't get it to work you might have to try something more extreme like https://developer.genesys.cloud/blog/2022-03-22-troubleshooting-data-actions/ to see what is going wrong.
Strange thing is, that if I paste the bearer and token direct in the configuration the request goes on, so someting with the translation of the values seems to be not OK I guess.
I think I found something.
When I take the token from Postman and paste it into the request the request works.
If I check if the variable ${authResponse.access_token} gets filled with a value from the custom authentication it seems to work. But when I compare the tokens the one that I get in Genesys is shorter.
The shorter one doesn't work when I paste it directly into the request, so because I am missing some characters the request fails.
Now the question is, is there a length limit in the custom authentication request that I might bump into?
It appears that the authentication information is in the form of a JWT. Putting the two authentication examples into a base64 decoder there are differences between the two examples you provided
Working
"aud":"https://redacted.com"
"roles":["Connector.FullAccess"]
Not working
"aud":"00000002-0000-0000-c000-000000000000"
roles not present
Based on your results so far it seems like it should be possible to get this to work. The problem appears to be that the JWT that is being created by the request from postman is different than the JWT created by the data action authentication action, indicating that they are making subtly different requests. You might look at the console in postman to see exactly what is being sent during authentication and compare it to the results of testing the authentication action in test mode, or the more extreme approach of running your data action through a proxy to see what is going on.
