Overview
For a post-login action, when triggering an MFA challenge (api.authentication.challengeWith) the next action will not have the event.request object details anymore from the login request.
Applies To
- Actions
- Multifactor Authentication (MFA)
Solution
This is the expected behavior currently. This is due to a current limitation in Actions:
- “A new event.request object is issued anytime an Action flow is suspended and then subsequently resumed (for example, due to a redirect or MFA challenge).”