SSH auth with Python - Random "Keyboard Interactive Authentication" pop-up

[powerponch]

Hello. I am currently running a python script from a custom button which logins to a router. The login works normally OK, however in some cases a pop-up appears ("Keyboard Interactive Authentication") and asks for manual password input.

Since my script is intended to run without human supervision, this is an issue. Moreover, I haven't been able to determine under which circumstances this pop-up appears.

Does somebody know how to suppress the pop-up?

Below the code I'm using for login:

cmd = "/SSH2 /L %s /PASSWORD %s /C AES-128 /M SHA1 %s" % (HOST_USERNAME, HOST_PASSWORD, HOST)

crt.Session.Connect(cmd)

[bgagnon]

Hi powerponch,

What version of SecureCRT are you using?

On what OS?

For the remotes where you see the dialog, it likely means that keyboard-interactive authentication is required. This is different than password authentication (though it often looks similar to the end user). RFC 4256 details keyboard-interactive authentication.

Getting Trace Options output to those devices should show what authentication method is supported.

You may need to adjust the connection method in your script and handle the possible prompts (notice what's in the screenshot is Enter PASSCODE:).

Or, if v8.5 or later, you may be able to leverage these features:

Changes in SecureCRT 8.5 (Beta 1) -- June 28, 2018
--------------------------------------------------
New features:

• Added a session INI-file-only option "Keyboard Interactive Prompt" that allows the expected prompt for keyboard-interactive authentication to be specified.

• Added a command-line flag /KEYBOARDINTERACTIVEPROMPT that allows the keyboard interactive prompt to be specified for SSH2 sessions.

[powerponch]

Thank you for the quick reply!

I am running SecureCRT v.8.5 on Windows 10. Is it possible to apply a fix or a flag for suppressing the pop-up?

It is of crucial importance given that the script is executed on a scheduled basis via Windows Scheduled Tasks, and it is not being executed when this pop-up appears because there is nobody to input the password.

As I mentioned, this happens in random occasions. More than often the login runs smoothly with the python code.

This is a screenshot of the pop-up that I'm getting:

[bgagnon]

Hi powerponch,

I'm sort of feeling like you did not read my post at all.

Do you have to enter something when prompted? If so, then this authentication method (keyboard-interactive) is what the remote requires so it will need to be handled. It is not the password authentication method, it is keyboard-interactive.

If you connect to a mix of remotes that require either password or keyboard-interactive then you will have to authenticate within the script.

For example:

• Wait for prompts (with WaitForStrings()) that may either have password or passcode in them
  
  
• Send appropriate response

[powerponch]

Hello. Sorry for the confusion. I did not quite get you first reply.
When the pop-up appears, I need to input the password for SSH authentication. Afterwards, my script continues its normal execution.

I am using a crt.Sleep(2000) command after the Session.Connect().

[bgagnon]

Hi powerponch,

I guess I am still not making it clear.

In simplest terms, you have remotes/devices that require two different methods of authentication. Therefore, you would need to use two different command-lines to handle each.

So you either have to:

• Be able to narrow down which requires password and which requires keyboard-interactive and connect to each with a different command-line.
  
  
• Handle both types within the script somehow. This requires being able to distinguish between the two.

If you opt for the latter option, what I suggest is you connect manually to a device that succeeds with your current command-line and collect Trace Options output (instructions were in a prior post). Then also connect manually to one of the devices that results in the pop-up you are reporting and collect Trace Options output from that.

You will want to have Display logon prompts in terminal window enabled in the sessions you connect manually (or in Default session if it's an ad hoc connection). That option is found in the Connection / Logon Actions category of Session Options.