https://community.cisco.com/t5/deployment-strategy/ubuntu-winscp-verified-push/m-p/5349359#M313 <P>I don't know the answer.</P> <P>As I understand it, PAM is used to trigger Duo in this case.<BR />I suspect if you create a PAM configuration to treat SSH differently from SCP (you would probably need to add an additional PAM service), then you could have PAM call Duo with different configurations.</P> Sun, 23 Nov 2025 19:31:24 GMT Philip D'Ath 2025-11-23T19:31:24Z https://community.cisco.com/t5/deployment-strategy/ubuntu-winscp-verified-push/m-p/5349149#M312 <P>I have Duo MFA setup on Ubuntu servers.&nbsp; I have Verified Push configured in the policy.&nbsp; All is working fine and I can successfully SSH into the servers and use Verified Push.&nbsp; However, when I try logging into a server via WinSCP, I am not given the Verified Push code.&nbsp; I receive a prompt to enter a code in the Duo App.&nbsp; But no code.&nbsp; So I am unable to login.&nbsp; Is there a way to force WinSCP to use "push" while SSH to use Verified Push?&nbsp; Thanks.</P> Fri, 21 Nov 2025 21:27:27 GMT https://community.cisco.com/t5/deployment-strategy/ubuntu-winscp-verified-push/m-p/5349149#M312 peter-supply 2025-11-21T21:27:27Z https://community.cisco.com/t5/deployment-strategy/ubuntu-winscp-verified-push/m-p/5349359#M313 <P>I don't know the answer.</P> <P>As I understand it, PAM is used to trigger Duo in this case.<BR />I suspect if you create a PAM configuration to treat SSH differently from SCP (you would probably need to add an additional PAM service), then you could have PAM call Duo with different configurations.</P> Sun, 23 Nov 2025 19:31:24 GMT https://community.cisco.com/t5/deployment-strategy/ubuntu-winscp-verified-push/m-p/5349359#M313 Philip D'Ath 2025-11-23T19:31:24Z