I believe there is a bug in REST Resource Authentication

[john_mollberg]

• Goal: Our API has custom authentication. I am attempting to parse the required field from an auth request and pass it into a header on the resource, and am unable to reference the variable.

• Steps: I tried referencing the created variable in many different ways and I can't figure out how to do it.

• Details:
  I'm not sure how to proceed. We have custom auth in our app and I'm unable to reference the variable created in the authentication flow within my API resource headers. The docs here say to "Pass the authentication token" but they don't say how to reference the actual variable - it looks like it's just a hardcoded string in the example screenshot.

here is the link to our (private) resource we're trying to set up if that's helpful.

I believe that this bug is maybe the same as this bug, but different from the merged bug

• Screenshots:
  

  

• App json export:

[Tess]

Hi @john_mollberg,

The header looks good in your screenshot. Can we see how you set the AUTHORIZATION_TOKEN? (I can't access your resource link)

Note that the variable must be created in the custom auth workflow steps, and not in the refresh auth workflow section. Usually, the define a variable step will look something like the below screenshot, where http3.body is an exported response from a previous auth step, such as an API request step:

You can create an app query with your resource, trigger the re-auth, and preview the query to see how AUTHORIZATION_TOKEN is getting defined.