Different inactivityTimeout in a MFA environment

[Cantor, Scott]

> However, if I'm not mistaken, it looks the inactivityTimeout
> from the  outer authn/MFA overrules my configuration.

That's correct, it wraps the other results so it can't be shorter than those.

> If I'm right, how can achieve a setup with different
> inactivityTimeout based on the used subflow in a MFA
> environment?

No direct or simple way. It's possible to implement a custom reuseCondition that can attach to the MFA flow and dig into what the embedded results were and enforce a custom timeout programmatically.

-- Scott