Start with a fresh authentication request to the identity provider, rather than adding a separate app password. A normal SSO redirect isn't enough by itself if the provider can silently reuse the existing session.
For OpenID Connect, look at max_age=0 or prompt=login, then validate the returned ID token and check auth_time against the freshness window you require. Check Google's current documentation and test the behavior before relying on either option. Provider support and the proof the user actually has to provide can vary.
Also make sure the returning identity matches the signed-in account, and tie the confirmation to the action and session that requested it. Fresh authentication doesn't automatically mean MFA, so request or enforce a stronger method separately if the action needs it.
_x92!drainruler.4:
That distinction matters. A recent authentication time tells you when authentication happened, not necessarily whether a second factor was used.