|Cannot save proxy authentication details [message #336357]
||Tue, 09 June 2009 15:30
| Ben Turner
Registered: July 2009
I have a long standing problem with saving my proxy authentication |
settings on Eclipse, which I have finally decided to get to the bottom of.
On fresh installs of Eclipse 3.4.2 and 3.5-RC3, I have started a brand new
workspace. I did this as starting with an old workspace means that the
Preferences->General->Network Connections menu is pre-populated, and it is
here I am having problems so I wanted a brand new empty menu screen.
Then, on Eclipse 3.4.2, I select "Manual Proxy Configuration" and input my
proxy server. This is fine and if I click "Apply" then "OK" it gets saved
to the ECLIPSE/configuration/.settings/org.eclipse.core.net.prefs file.
But if I tick the "Enable Proxy Authentication" box, and enter any details
into the User Name and Password boxes, these details are never saved. This
appears to have been the case for ages with my old 3.4 installation, and
now is happening on both fresh installs on 3.4.2 and 3.5-RC3 which leads
me to conclude two things:
(a) This is quite unlikely to be a bug with eclipse, as it's a fairly
basic feature that's broken here.
(b) Whatever is causing the problem is probably specific to my
workstation. Maybe some curious security setup.
Unable to find exactly HOW the proxy authentication details are stored by
eclipse (I'm guessing not to a plain text file), I then checked my
workspace .log file, which had the following stack trace :
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.core.net 4 0 2009-06-09 16:09:13.200
!MESSAGE No password provided.
org.eclipse.equinox.security.storage.StorageException: No password
Can anyone shine any light on this stack trace ? I certainly HAVE provided
a value for "Password" on the Network connections preferences page. So I'm
guessing it's trying to use a password to store the underlying details
somewhere ? But I am stumped as to what context it's looking for a
password. This problem basically stops me from using the upgrade manager -
I used to get it working intermittently, but in recent months it just
fails without prompting me for username or password at all.
Thanks for any advice or assistance,
Powered by FUDForum
. Page generated in 0.14253 seconds