{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/f11fd99512cc464ab0e9a40aa7870e97\" frameborder=\"0\" width=\"2218\" height=\"1663\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1663,"width":2218,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1663,"thumbnail_width":2218,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/f11fd99512cc464ab0e9a40aa7870e97-6daeaca1663de138.gif","duration":4159.246,"title":"Authsignal Walkthrough - Adaptive MFA","description":"In this Loom, I show how to track an AuthSignal action called Payment and use its state to control whether I proceed or step up authentication. I start with the outcome set to challenge, then change it to allow, and explain that my backend should use the returned state. I add a rule to challenge when a custom amount is greater than 1000, so 1000 and under allows, and 1001 and above requires a challenge. When challenged, AuthSignal returns a URL and I pass a redirect URL to return with a token. I requested nothing from viewers directly, but the flow demonstrates copying and validating the returned token on my server, which returns ChallengeSucceeded, plus the user ID and action code."}