#359 Trouble setting remote configuration

Georg Schild

We are unable to set up a remote sonar location as remote configuration.

When defining https://<ourdomain>/sonar/profiles/export?format=checkstyle&language=java&name=<ourProfile> with correct authentication credentials, the dialog seems to ignore the "OK" request.
In the workspace log an exception is shown:

java.lang.IllegalArgumentException: Node path "eclipse-cs//<is-this-something-secure?>" is not valid.
at org.eclipse.equinox.internal.security.storage.SecurePreferences.validatePath(SecurePreferences.java:361)
at org.eclipse.equinox.internal.security.storage.SecurePreferences.node(SecurePreferences.java:95)
at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.node(SecurePreferencesWrapper.java:83)
at net.sf.eclipsecs.core.config.configtypes.RemoteConfigurationType$RemoteConfigAuthenticator.storeCredentials(RemoteConfigurationType.java:416)
at net.sf.eclipsecs.ui.config.configtypes.RemoteConfigurationEditor.getEditedWorkingCopy(RemoteConfigurationEditor.java:232)
at net.sf.eclipsecs.ui.config.CheckConfigurationPropertiesDialog.okPressed(CheckConfigurationPropertiesDialog.java:310)

This used to work in a previous version of the plugin (~9 months ago, not exactly sure which version this was).


  • Georg Schild
    Georg Schild

    So there's part of the "bad" node path missing. I'm not sure if this hash (or whatever it is) is safe to show.

    java.lang.IllegalArgumentException: Node path "eclipse-cs//<is-this-something-secure?>" is not valid.

  • Thanks for the bug report, I could reproduce the problem.
    The hash is just an Base64 encoded MD5 hash of the location URL.
    The purpose is to store the credentials in the equinox secure storage, related to the configuration file URL. However since the secure storage paths are limited to 128 characters I've chosen this hash conversion to ensure the length limits are met, independent of the input resource URL.

    Now, the problem is that for some URLs out comes something like this:

    Here the problem is that 2 consecutive slashes are not allowed in such a secure storage path. I suppose you've hit a similar problem.

    I will adapt the hash generation to deal with this particular problem.

    • status: open --> closed
    • assigned_to: Lars Koedderitzsch
  • Georg Schild
    Georg Schild

    The Snapshot fixes the issue. Thanks!