A city jump host requires interactive MFA, which breaks unattended tunnel automation. What planning adjustment is appropriate?
Select an answer to reveal the explanation.
Short Explanation
If the jump box wants a human to tap MFA, your unattended tunnel script just hit a locked door with manners. Plan around interactive auth instead of trying to outlaw MFA for convenience. Some pivots need a person in the loop—that is a schedule fact, not a failure.
Full Explanation
Interactive MFA on jump hosts constrains which forwarding or tunneling automations can run without a human present. Engagement planning should reflect those authentication realities rather than attempting to weaken MFA controls. Sharing OTP codes publicly or demanding citywide MFA disablement is inappropriate. Feasible pivot designs respect interactive auth constraints.