-
-
Notifications
You must be signed in to change notification settings - Fork 37
sftp issues #1
Comments
Since new version 0.15.4:
All the new things work for FTP connections too. |
@mkloubert Thanks for the update. I tried the new version on different machines, seems I couldn't connect the server even with |
You also have to encode that path and you should not use double backslashes: My suggestion is, to store that file into your user directory, something like |
BTW.: |
@mkloubert Awesome! Both explicit credentials in URI and through |
|
@mkloubert That documentation says it's a keyboard-interactive user authentication if primary authentication fails. I am a little confused. Does that mean I have to put a fake password in the URI? How did it work for you? Could you please give a demo on that? Thank you so much! |
This setting "simulates" an user interaction and depends on the SSH config on the server. The underlying module is non-interactive. You always have to setup the real password in the URL or an auth file, no fake one! If the server does not accept the "standard" login, it sends a request for a "try keyboard" event and the module does a secondary login method, defined with the password, you have defined. |
@mkloubert Thanks for the explanation, I understand now. |
Thats right, I am using ssh2-sftp-client/ssh2 module for this. What do you mean with "RSA securID token"? Login with private / public key? If so: This is supported by the module and that extension. For this, you have to use |
The "RSA securID token" is something that replaces password. You may have a hard token or soft one, which changes every minutes. I tried to find some web pages explaining this, but unfortunately, just found this one: https://fermi.service-now.com/kb_view.do?sysparm_article=KB0011463 I know the extension relies on 3rd-party packages, probably I should open an issue there. |
Great extension! But I am facing some issues while using the sftp protocol:
Thanks!
The text was updated successfully, but these errors were encountered: