[jbosstools-issues] [JBoss JIRA] (JBIDE-19905) Connection token and authentication scheme are not saved

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-19905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073892#comment-13073892 ] 

Andre Dietisheim edited comment on JBIDE-19905 at 6/3/15 5:49 PM:
------------------------------------------------------------------

with the patch I now have the following when using basic auth:

# ASSERT: make sure that you have a connection in explorer that's using username & password and password stored to secure storage
# EXEC: restart Eclipse
# EXEC in explorer unfold your connection
# ASSERT: SSL connection dialog pops up
# EXEC: confirm it

Result:
An error dialog pops up telling me that my connection is unauthorized
!unauthorized.png!
in the Eclipse log I see the following
{code}
com.openshift.internal.restclient.http.UnauthorizedException: Unauthorized

	at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:208)
	at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:151)
	at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:130)
	at com.openshift.internal.restclient.http.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:92)
	at com.openshift.internal.restclient.DefaultClient.getVersion(DefaultClient.java:307)
	at com.openshift.internal.restclient.DefaultClient.getOpenShiftVersions(DefaultClient.java:283)
	at com.openshift.internal.restclient.DefaultClient.getOpenShiftAPIVersion(DefaultClient.java:297)
	at com.openshift.internal.restclient.DefaultClient.getTypeMappings(DefaultClient.java:332)
	at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:119)
	at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:113)
	at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:108)
	at org.jboss.tools.openshift.core.connection.Connection.get(Connection.java:309)
	at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:57)
	at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:124)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.io.IOException: Server returned HTTP response code: 401 for URL: https://localhost:8443/osapi
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1839)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440)
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
	at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:147)
	... 13 more
{code}
[~jcantrill] Is this expected, a different bug?



was (Author: adietish):
with the patch I now have the following when using basic auth:

# ASSERT: make sure that you have a connection in explorer that's using username & password and password stored to secure storage
# EXEC: restart Eclipse
# EXEC in explorer unfold your connection
# ASSERT: SSL connection dialog pops up
# EXEC: confirm it

Result:
An error dialog pops up telling me that my connection is unauthorized
!unauthorized.png!

[~jcantrill] Is this expected, a different bug?


> Connection token and authentication scheme are not saved
> --------------------------------------------------------
>
>                 Key: JBIDE-19905
>                 URL: https://issues.jboss.org/browse/JBIDE-19905
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.0.Beta1
>            Reporter: Jeff Cantrill
>            Assignee: Jeff Cantrill
>             Fix For: 4.3.0.Beta1
>
>         Attachments: unauthorized.png
>
>
> Fix saving of a user's token and the auth scheme for a server.  Might consider setting the username for a connection to user.getName() instead of user.getFullName()



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