-
-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSH in-browser and key authentication options exclusives? #946
Comments
I haven't tested this directly, but have you also confirmed the keyboard-interactive prompt in the SSH client after clicking Authorize in the browser? The client is going to wait for your input before checking whether the auth was successful or not. |
Yes, I did check that. When you hit enter in the shell, the shell hangs like when you did not authorized the connection. It's actually working well when only the "in-browser" option is activated. It would be nice to implement a feature that displays a "connection not authorized" message where the connection hasn't been validated by the user. This would clarify the connection status. |
Can you please tell me, how you configured that? I can't find any documentation about this feature. |
Ahh… cool! Really nice. As for your question about whether in-browser and key authentication are exclusives, to me it seems that they're actually inclusive. If you activate either, you can't use the in-browser auth alone, but your keys must match as well. This is actually great stuff and I am so happy, that I stumbled across this. |
edit: should have commented this in issue #972 |
I found that when I added a public key for the admin user in the browser, the last username part of my public key was deleted when I saved it. This may cause the local public key to not match the public key saved by the warpgate admin account when I connect with the public key, so I need to enter the admin user password to log in. Please fix it as soon as possible |
I've tried to reproduce the initial issue and couldn't. Could you try connecting with
|
Hello!
First of all, big thanks for this amazing project; it truly is a fantastic tool :)
Now, I've encountered an issue where, if I enable both the "in-browser" and "key" authentication methods for SSH, the in-browser validation appears to malfunction. Attempting to click the button to authorize the connection results in no action.
Cheers and thanks again!
The text was updated successfully, but these errors were encountered: