...
In the above, I have two devices registered, a phone and a tablet. The phone is set to be the primary device. The above requires interaction which in most cases is probably not a huge burden. Of course, there are some commands that do not present dialogs at the console. This would be things such as scp and NXNo Machine. For these types of commands, Duo will autopush the request to your out-of-band authentication method. If you have the app on a smartphone then the request will go there. If not, then a phone call will be made to the registered number. Clearly, the app on a smartphone is a much better way to handle that. There will be no prompt in your terminal window so you must remember to check your smartphone for the pushed request. However, it is also possible to send an authentication key as part of the command and that is particularly useful for those without a smartphone. Passing a key on the command line is probably easier than authenticating with a phone call. See the Advanced Setup section below for more information.
...
| Info |
|---|
If the pushed request, or the response to it, is delayed then NX No Machine connections may time out before they get established. One cause of delay could be that your phone is busy doing some other task, such as updating apps. Older phones may bog down and cause the Duo push response to get delayed due to not being able to effectively do more than one task at a time. If No Machine connections are not working then give FastX a try. |
...