Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Oomph » Silent failure of HTTPS authentication in Eclipse Installer
Silent failure of HTTPS authentication in Eclipse Installer [message #1842164] Thu, 10 June 2021 16:26 Go to next message
Elie Richa is currently offline Elie RichaFriend
Messages: 51
Registered: February 2016
Hello folks,

I'm using a product definition setup stored on a server that requires authentication. The same server also provides P2 repositories also with authentication.

The Eclipse Installer correctly prompts the User for credentials, but on Linux, using the option to save the password for future use is creating issues sometimes.

Here's the scenario, with Eclipse Installer version 1.21.0:

1. The installer prompts for my credentials (supposedly to update the product setup)
2. I enter correct credentials and ask to save them in the secure storage
3. The installer prompts for credentials again immediately.
4. I enter them correctly again and ask again to save them in the secure storage.
5. The installer is now happy, but I am not sure it managed to update the setup. It could be using a local cached version.
5. I proceed with the installation.
6. Later during the execution of P2 Director, the installer complains of not being able to access the P2 repository that requires authentication and offers to use an outdated cache.
7. Refusing the cached version stops the installation. The only choice is to accept to continue with an outdated P2 cache + a potentially outdate Oomph setup in the first place.

Looking at the installer log, I find the following exception that goes unnoticed:

!ENTRY org.eclipse.oomph.setup.core 4 0 2021-06-09 09:34:27.886
!MESSAGE Unable to locate secure storage module (
!STACK 0 Unable to locate secure storage module (
	at org.eclipse.oomph.preferences.util.PreferencesUtil$AutoRefreshSecurePreferencesWrapper.get(
	at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl$AuthorizationHandlerImpl.authorize(
	at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl$AuthorizationHandlerImpl.reauthorize(
	at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl$ConnectionHandler.process(
	at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl.createInputStream(
	at org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterImpl.createInputStream(
	at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl$ETagMirror$Worker.perform(
	at org.eclipse.oomph.util.WorkerPool$

The same scenario occurs sometimes with "Perform Setup Tasks" in Eclipse, but I can't find an exception anywhere.

Deleting ~/.eclipse/ seems to solve the issue. But it always comes back a few weeks later and I can't pinpoint why yet.

I found two potentially relevant reports on Bugzilla:

One mentions a conflict between 32bit and 64bit Eclipse versions, but that's not the case here. While multiple Eclipse versions exist, they are all 64bit versions.

I suspected it was happening when using different Eclipse versions, but one of the above Bugzillas confirms that the secure_storage format is stable and should happily serve different Eclipse versions.

Any ideas of what I could try out the next time this occurs?

And could the installer and setup executioner be improved to make authentication failures more visible instead of continuing somewhat silently?


Elie Richa, Ph.D
Software Engineer, AdaCore
Re: Silent failure of HTTPS authentication in Eclipse Installer [message #1842183 is a reply to message #1842164] Fri, 11 June 2021 05:53 Go to previous message
Ed Merks is currently offline Ed MerksFriend
Messages: 32111
Registered: July 2009
Senior Member
It would be good to learn the underlying cause. but I don't work regularly on Linux and have never see this type of problem. Once this problem occurs it would certainly be good to try to debug it at that point like I did with the 32/64 bit stuff. But as you can see, it's hard to get the correct people involved because all this stuff is free and no one feels it's their duty to work on such hard problems for free...

The implementation is intentionally such that a failed authentication will fall back to using a cached version but I suppose that could be changed. A failure to load a setup in the installer would generally end up prompting you for changing your network proxy settings so that would need some more attention. You can see that the loading is done on many threads so collecting the different failures from the different threads would also need attention. It's not entirely trivial...

Ed Merks
Professional Support:
Previous Topic:P2 Director creating an inconsistent configuration that crashes after restart
Next Topic:Can preferences of views (e.g. "Problems" view) be centralized via OOMPH
Goto Forum:

Current Time: Mon Dec 06 20:50:15 GMT 2021

Powered by FUDForum. Page generated in 0.01856 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top