Skip to Main Content
Forums

SQL Developer

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

SSH Tunnel fails with "No more authentication methods available"

Robert SchaeferDec 28 2019 — edited Jan 6 2020

With SQL Developer 19.4 i'm still receiving the error message "No more authentication methods available"  while connecting via SSH tunnel. The information in Doc ID 2575854.1 is inadequate, it just points out to regenerate the keys in OpenSSH format.

In my case I've already used keys in OpenSSH format and beginning with 19.2 the connections started to fail. I regenerated the private public keys by using "ssh-keygen" on different platforms (MacOS, Linux) and protocols (RSA 2048, RSA 4096). I also converted the key to RFC4716 format (see https://carsandcode.com/2019/11/21/solved-sql-developer-19-2-no-more-authentication-methods-available-when-using-ssh-connections/). All formats are no longer accepted. In 19.1 the SSH tunnel works fine for me.

What has been changed in SQL Developer? Any clarifications about the OpenSSH format to be used?
This post has been answered by John McGinnis-Oracle on Jan 2 2020
Jump to Answer

Comments

Answer

What platform are you on? What are the permissions for the keyfile and directory containing the keyfile? In particular, are the file/directory permission set to permit only the current user to read them? Our new library defaults to enforcing the recommended SSH security practice of having keyfiles be readable by only the current user.

Marked as Answer by Robert Schaefer · Jan 2 2020
3 people found this helpful
Robert Schaefer

Hi John,

i'm running SQL Developer on MacOS 10.15.2. The file permission for the private key is limited to "rw-------" (600). But the directory (".ssh") containing the keys has a lower permission level with "rwxr-xr-x". I limited it to "rwx------" and now the SSH Connections in SQL Developer are working again! Great support, thank you!

1 person found this helpful

I'm glad that you were able to solve your issue. The lack of proper feedback with our new SSH library is something I am looking into. In a future release I hope to provide detailed information when we run into a configuration issue.

2 people found this helpful
YujiSoftware

I had the same problem in my environment.
(SQLDeveloper version 21.2.1.204, build 204.1703)

After investigating the cause, I found that it was a bug in Apache Mina SSHD 2.6.0.
https://issues.apache.org/jira/browse/SSHD-1105
(I've confirmed that this fix solves the problem)

This bug has been fixed in sshd-2.7.0.

I want you to update the version of sshd included in SQLDeveloper.

John McGinnis-Oracle

Thanks for the update. Can you test in your environment with our 21.4.3 release? We updated to sshd-2.7.0 in that release, so hopefully it works out of the box.

1 person found this helpful
YujiSoftware

Thank you for your comment.
After upgrading, it worked fine!
(SQL Developer version 21.4.3.063, build 063.0100)

The Japanese page is still 21.2.1, so I'd be happy if you could update it.
https://www.oracle.com/jp/tools/downloads/sqldev-downloads.html

1 - 6

Post Details

Added on Dec 28 2019
#sql-developer
6 comments
11,440 views