Dynamic HTTP Header / Merge Fields

Bump. Any ideas I can test?

Hey @BWind - Have you enabled the Proxy with this data source?

This is the documentation that talks about how to insert merge variables form Apex into the HTTP Requests.
https://docs.skuid.com/latest/v2/en/data/authentication-and-skuid.html#on-the-apex-merge-variable

@annajosephine Thank you for the response! 

1. Yes, I have toggled the ‘Use Proxy’ to true for this data source. 
2. I have followed the directions in the linked document and cannot see that the class is being called. I’ve also added the suggested assert statement and still do not receive the error. 

system.assert(false,'The class was called');

The only error I receive is “Bearer token is missing in the HTTP request authorization header.” which is where I’m trying to use the merge variable:
 

Can you confirm that the $Apex merge variables should be able to be used in the common request headers section? 

This thread outlines almost the exact same issue I’m seeing, except that they are inserting it into the body whereas im inserting it into the headers. However, the experience is very similar. Do you know if there were any updates out of that convo? 

@annajosephine Just checking in - any thoughts on if this is an existing bug / issue? 

Just noting that I was never able to solve this issue with passing a dynamic header. In our case, I was able to work around the issue because the API we were integrating with is custom built by our team, so I could pass the value as a query parameter.