[jbosstools-issues] [JBoss JIRA] (JBIDE-25165) Server Adapter Editor: pops up 2 connection dialogs if I open the editor while my connection has no pw stored
Andre Dietisheim (JIRA)
issues at jboss.org
Mon Oct 9 09:54:00 EDT 2017
[ https://issues.jboss.org/browse/JBIDE-25165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andre Dietisheim updated JBIDE-25165:
-------------------------------------
Description:
# ASSERT: make sure that you have a connection where the password is *NOT* stored
# ASSERT: have a server adapter that is using this connection
# EXEC: restart Eclipse
# EXEC: in the freshly started Eclipse: open the editor for your server adapter
# ASSERT: connection wizard pops up prompting you to provide the password
# EXEC: "Cancel" the dialog
Result:
The connection wizard pops up a 2nd time
Expected result:
I should not have to cancel the dialog a 2nd time
was:
# ASSERT: make sure that you have a connection where the password is *NOT* stored
# ASSERT: have a server adapter that is using this connection
# EXEC: restart Eclipse
# EXEC: in the freshly started Eclipse: open the editor for your server adapter
# ASSERT: connection wizard pops up prompting you to provide the password
# EXEC: "Cancel" the dialog
Result:
The connection wizard pops up a 2nd time
Expected result:
I should not have to cancel the dialog a 2nd time
The 2 stack traces (for both cancels) are the following:
{code}
!ENTRY org.eclipse.core.jobs 4 2 2017-10-09 15:28:21.364
!MESSAGE An internal error occurred during: "Loading OpenShift Server Resources...".
!STACK 0
com.openshift.restclient.authorization.UnauthorizedException: Unauthorized to access resource. You can access the server using Basic authentication.
at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:110)
at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65)
at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
at okhttp3.RealCall.execute(RealCall.java:57)
at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.tryAuth(OpenShiftAuthenticator.java:106)
at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.authenticate(OpenShiftAuthenticator.java:62)
at okhttp3.internal.http.HttpEngine.followUpRequest(HttpEngine.java:946)
at okhttp3.RealCall.getResponse(RealCall.java:279)
at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:201)
at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:54)
at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
at okhttp3.RealCall.execute(RealCall.java:57)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:258)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:222)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:210)
at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:333)
at com.openshift.internal.restclient.authorization.AuthorizationContext.isAuthorized(AuthorizationContext.java:65)
at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:236)
at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:225)
at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:530)
at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:473)
at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getResource(OpenShiftServerUtils.java:424)
at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getResource(OpenShiftServerUtils.java:374)
at org.jboss.tools.openshift.internal.ui.server.OpenShiftServerEditorSection$LoadProjectsJob.run(OpenShiftServerEditorSection.java:723)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
{code}
{code}
com.openshift.restclient.authorization.UnauthorizedException: Unauthorized to access resource. You can access the server using Basic authentication.
at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:110)
at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65)
at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
at okhttp3.RealCall.execute(RealCall.java:57)
at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.tryAuth(OpenShiftAuthenticator.java:106)
at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.authenticate(OpenShiftAuthenticator.java:62)
at okhttp3.internal.http.HttpEngine.followUpRequest(HttpEngine.java:946)
at okhttp3.RealCall.getResponse(RealCall.java:279)
at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:201)
at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:54)
at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
at okhttp3.RealCall.execute(RealCall.java:57)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:258)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:229)
at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:162)
at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:150)
at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:137)
at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:471)
at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:465)
at org.jboss.tools.openshift.internal.ui.server.ServerResourceViewModel$ResourceTreeItemsFactory.createChildren(ServerResourceViewModel.java:232)
at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.loadChildren(ObservableTreeItem.java:69)
at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.load(ObservableTreeItem.java:56)
at org.jboss.tools.openshift.internal.ui.server.ServerResourceViewModel.loadServices(ServerResourceViewModel.java:211)
at org.jboss.tools.openshift.internal.ui.server.ServerResourceViewModel.loadResources(ServerResourceViewModel.java:195)
at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardPageModel.loadResources(ServerSettingsWizardPageModel.java:360)
at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardPageModel.loadResources(ServerSettingsWizardPageModel.java:352)
at org.jboss.tools.openshift.internal.ui.server.OpenShiftServerEditorSection$2$1.run(OpenShiftServerEditorSection.java:202)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
{code}
> Server Adapter Editor: pops up 2 connection dialogs if I open the editor while my connection has no pw stored
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25165
> URL: https://issues.jboss.org/browse/JBIDE-25165
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift, server_adapter_editor
> Fix For: 4.5.x
>
>
> # ASSERT: make sure that you have a connection where the password is *NOT* stored
> # ASSERT: have a server adapter that is using this connection
> # EXEC: restart Eclipse
> # EXEC: in the freshly started Eclipse: open the editor for your server adapter
> # ASSERT: connection wizard pops up prompting you to provide the password
> # EXEC: "Cancel" the dialog
> Result:
> The connection wizard pops up a 2nd time
> Expected result:
> I should not have to cancel the dialog a 2nd time
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jbosstools-issues
mailing list