Hi @Terry_Hopper,
Thanks so much for your input here!
When I make a --digest auth call, I end up with a nonce (and an “opaque”) value in the collection of output headers that I can access in the following step - no error handler needed:
Digest realm="bsns-admin"
qop="auth,auth-int"
nonce="6f6dfb807bc5d7e84d2b"
opaque="934a0ef735ce666370ede"
I’ve seen another proposed solution, but there is just a picture of the scenario flow - no details on the config: Digest Auth for my Clock PMS custom app - #4 by andrtvrd
What do I do with the nonce to achieve digest authorization?
My understanding is that I need to hash per MD5, but not sure what all to stick in there or how to invoke the results in a subsequent HTTP call
Thanks!
for reference: What is digest authentication? - Stack Overflow