Added option which will try "keyboard-interactive" user authentication #32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added ability to handle "keyboard-interactive" user authentication if primary authentication fails.
My use case for this feature is discussed in #31 . This works perfectly with user authentication when SSH server setup to use public key and multi-factor authentication. To try this out you can setup an SSH host on AWS as discussed in this article: https://www.middlewareinventory.com/blog/aws-mfa-ssh-ec2-setup/ and ssh to it.
Options for such a setup would be as simple as:
If "keyboard-interactive" authentication is initiated by the server, prompts passed in by the server will be shown, and the library will wait for keyboard input from the user before proceeding.
Note that if is set to true but "keyboard-interactive" authentication is not initiated by the server, the option will do nothing.
The README.md file has been updated to include a description of the new
tryKeyboardInteractive
option (which was lifted from thessh2
library's own documentation).