I have same problem with 4.0, I hope someone has an answer.

Hi,

Possibly the directory structure containing your connections.xml is not writable.  Check the value of Help -> About -> Properties -> ide.user.dir.

If the directory specified there is not writable, then neither will the connections.xml file further down below the system4.0.0.12.27 folder for 4.0 EA1.

This can happen if your company policy defaults your ide.user.dir privilege to read-only, whether on a network drive or even on your local disk.

You can override the ide.user.dir default value by placing the following line in your ...\sqldeveloper\sqldeveloper\bin\sqldeveloper.conf file: 

AddVMOption -Dide.user.dir=C:/path_to_your_preferrable_location

Hope this helps,

Gary

SQL Developer Team

I have tried the instructions as provided above and still experience the same issue.  On the Logging Page it indicates that SQL Developer is not able to decrypt the passwords for the connections.

I hope this provides some insight to the issue that a few of us are having since upgrading to the 4.0.0.12 build 12.27

When you upgraded from 3 to 4, did you manually copy your connections and settings files over?

No, I believe it asked if I wanted to import the settings from he prior version and I said yes.

ro*323171*on wrote:

 

No, I believe it asked if I wanted to import the settings from he prior version and I said yes.

That is exactly what I did too and it (EA4) cannot remember/recognize my saved passwords, looks like encryption algorithm was probably changed?

Raj

Was there ever a solution or work around to this issue?  It would sure save a lot of time if this fuctionality was working correctly.

The password logic has changed when moving settings files around from 3.2 to 4. The developer will take another look at this.

As Jeff mentioned, there were some changes made to how connections are stored, and in particular how passwords are stored. This shouldn't impact users that migrate settings, and in our testing, it doesn't.

However, there are obviously cases where there is an impact. If you could provide detailed steps of how you upgraded from 3.2 to 4.0 and when the issue arose, I would appreciate it.

In particular:

• Confirm that you did migrate settings from 3.2. When you did, did you pick a particular version, or the default version presented?
• When you first launched 4.0, did the passwords work?
• Are the passwords working for any connections? Existing connections? New Connections?
• How many connections do you have?

Hopefully this will help create a testcase so we can track down the problem.

- John

SQL Developer Team

I did migrate from the default version that was presented which was 3.2.20.09.87 (I believe).  It seems like the first time I opened 4.0 the passwords did work.  I have 48 connections and the results were the same for each of the connections.

Since I last posted this morning I did find :

https://forums.oracle.com/thread/2299451?tstart=0

I tried the steps listed here and had no luck but if instead of importing the exported file I browsed and imported the connections.xml file from the prior version it seems to work.  I have opened it and closed it several times and it seems to still remember the connection passwords (unkown if the issue will return or not).

I just installed 4.0 into same directory as 3.2 and let it migrate my settings. it remembers new passwords, but always complains about old ones. I'd hate to remove over 25 connections in my list and add them back manually.

Always install into an empty directory!  From the release notes:

SQL Developer 4.0 Release Notes</title><meta name="Title" content="SQL Developer 4.0 Release Not…

"All new releases of SQL Developer require a full installation. Download and unzip the file into an empty folder"