I am trying to connect to a REST API that requires digest authentication. I created a REST API resource, selected Digest Auth from the authentication dropdown, and entered the Username and Password.
Afterward, I created a query that utilizes the previously defined resource. However, when I attempt to make a request, I encounter the following error:
[3,nonce="some-hidden-value",4] from header [Digest realm="Staging App", qop="auth", algorithm=MD5, nonce="some-hidden-value", opaque="some-hidden-value"]
put_metadata
from put_metadata response(put_metadata)
in put_metadata.trigger()(put_metadata)
headers: {Content-Type: "application/json"}
Content-Type: "application/json"
body: {some-property: "some-value"}
some-property: "some-value"
environment: "staging"
The credentials work perfectly when tested in Postman.
This particular authentication method isn't something I'm super familiar with, but I did some testing and was able to compare the authorization header generated by Retool with the one generated by Postman.
There doesn't seem to be an obvious discrepancy that would explain the behavior that you're seeing. Are you able to share a screenshot showing the error message as it appears within Retool?
Hi Darren, thank you for getting back to me. Unfortunately, I couldn’t get it to work, so I decided to create an AWS Lambda to serve as a proxy for making the digest-authenticated request. I’m unsure if the service I’m trying to access (which I don’t own) requires additional configurations that Retool doesn’t support or if there’s another issue, but the provided digest authentication feature didn’t work for me.
I'm glad you were able to come up with a workaround, at least! I definitely want to figure out what might be causing this. Would you mind sending me the contents of the www-authenticate header that you get back from the API? When using Postman, you can tell it to not automatically retry the request.
Would you mind sending me the contents of the 
