I've been developing an application that hits the api/1/saml_assertion, https://developers.onelogin.com/api-docs/1/saml-assertions/generate-saml-assertion , endpoint of OneLogin with Duo as my MFA. There are a couple of device elements that get returned that I'm unsure what to do with and can't seem to find any documentation on it. These elements are duo_sig_request and duo_api_hostname.
duo_sig_request looks like this:
'duo_sig_request': 'TX|<base64 encoded elements>|<what looks like a sha1 hash>:APP|<base64 encoded elements>|<what looks like a sha1 hash>'
duo_api_hostname is just the API url for Duo.
The base64 encoded elements are the user's email, what I'm assuming is the user's Duo ID, and a number that I'm unsure about since it changes with every request.
I'm assuming this information is intended to be used against https://duo.com/docs/authapi#/auth to actually trigger a Duo push, text, or call, and that sha1 is the hmac signature for Duo auth.
Has anyone successfully done what I'm attempting and can affirm that what I'm assuming is correct? Also can anyone tell me what that third element is (a device ID that changes per request maybe?) and what TX vs APP are?
Thanks in advance for any help!!