[jbosstools-issues] [JBoss JIRA] (JBIDE-21902) Connecting to a OS 3 Server adapter on restarted Eclipse throws error

[Jeff Cantrill (JIRA)]

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

Jeff Cantrill commented on JBIDE-21902:
---------------------------------------

[~fbricon] [~mlabuda] I'm having some issues reproducing this.  The results I get are an error in the log on the initial attempt to retrieve services, this is a debug log and presumably is not there if you dont have trace on.  It subsequently is able to connect on retry for me regardless if i have saved a password or not.  I presume this has something to do with the way the auth policy is set up for the server where it ignores password and lets anyone in.  I would be interested in seeing what the behavior is against a server that actually requires authentication with a legitimate token.  Do you have a setup where you it actually does not save a password and it additionally does not accept an empty password.

> Connecting to a OS 3 Server adapter on restarted Eclipse throws error
> ---------------------------------------------------------------------
>
>                 Key: JBIDE-21902
>                 URL: https://issues.jboss.org/browse/JBIDE-21902
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.1.CR1
>            Reporter: Marián Labuda
>            Assignee: Jeff Cantrill
>            Priority: Blocker
>              Labels: openshift_v3
>             Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> If I am having an OpenShift 3 Server Adapter in Servers view and I restart IDE, I have to fill in credentials again to start OS 3 server adapter. After filling valid credentials using local CDK OS 3.2, following error pops up and server is still stopped. Following attempt to start the server adapter finish successfully (it is because connection is already established, but in first attempt although I was prompted to fill in credentials and connection was some time during the process established, it seems the server adapter was not able to comprehend it.
> {code}
> The OpenShift service for server eap-app at OpenShift 3 (10.3.2.2) could not be reached.
> com.openshift.restclient.authorization.UnauthorizedException: Unauthorized to access resource. You can access the server using Basic authentication.
> 	at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:485)
> 	at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:158)
> 	at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:139)
> 	at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:387)
> 	at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:287)
> 	at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:276)
> 	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.pollState(OpenShiftLaunchController.java:73)
> 	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:56)
> 	at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> 	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> 	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> 	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> 	at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
> 	at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> 	at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)