[jbosstools-issues] [JBoss JIRA] (JBIDE-20344) Secure storage error upon creating a connection to stg v3 server or refreshing an existing one

Jeff Cantrill (JIRA) issues at jboss.org
Fri Aug 21 09:05:27 EDT 2015


     [ https://issues.jboss.org/browse/JBIDE-20344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Cantrill reassigned JBIDE-20344:
-------------------------------------

    Resolution:     (was: Cannot Reproduce Bug)
      Assignee: Jeff Cantrill


Reopening as the issue is providing a trailing slash or not for the base url causes problems.  The token doesnt get saved so therefore it doesnt get passed onwards and causes other general usability issues.

> Secure storage error upon creating a connection to stg v3 server or refreshing an existing one
> ----------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-20344
>                 URL: https://issues.jboss.org/browse/JBIDE-20344
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.0.Beta2
>         Environment: nightly build of JBDS Beta2-v20150721-2301-B78
>            Reporter: Marián Labuda
>            Assignee: Jeff Cantrill
>            Priority: Critical
>              Labels: connection, respin-a
>             Fix For: 4.3.0.Beta2
>
>
> Right after new OpenShift v3 connection to staging server is created OR the existing OpenShift v3 connection to stagins server is refreshed, there is an error in error log. The error pop up twice in error log. After calling refresh on a connection, connection is refreshed altough the existance of the error.
> Stack trace of error:
> {code}
> Exception saving connection property
> org.jboss.tools.openshift.internal.common.core.security.SecureStoreException: Could not remove value token
> 	at org.jboss.tools.openshift.internal.common.core.security.SecureStore.remove(SecureStore.java:75)
> 	at org.jboss.tools.openshift.core.connection.Connection.saveOrClear(Connection.java:181)
> 	at org.jboss.tools.openshift.core.connection.Connection.save(Connection.java:151)
> 	at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:200)
> 	at org.jboss.tools.openshift.core.connection.Connection.refresh(Connection.java:299)
> 	at org.jboss.tools.openshift.internal.ui.handler.RefreshResourceHandler$1.doRun(RefreshResourceHandler.java:85)
> 	at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.IllegalArgumentException: Node path "org.jboss.tools.openshift.core/console.stg.openshift.com//mlabuda at redhat.com" 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 org.jboss.tools.openshift.internal.common.core.security.SecureStore.getNode(SecureStore.java:114)
> 	at org.jboss.tools.openshift.internal.common.core.security.SecureStore.remove(SecureStore.java:72)
> 	... 7 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)



More information about the jbosstools-issues mailing list