[jbosstools-issues] [JBoss JIRA] (JBIDE-20289) Connection wizard: Cannot log into v3 STG
Andre Dietisheim (JIRA)
issues at jboss.org
Thu Jul 16 06:31:03 EDT 2015
[ https://issues.jboss.org/browse/JBIDE-20289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andre Dietisheim updated JBIDE-20289:
-------------------------------------
Steps to Reproduce:
# EXEC: use an existing connection to https://console.stg.openshift.com
# EXEC: in case you're using an existing connection: launch application wizard and pick your connection to stg and hit "Next"
# ASSERT: you're told to obtain an API token
# EXEC: hit "retrieve", log in, copy the token in the dialog and paste it into the form
# EXEC: hit "Next"
Result:
!cannot-login-stg.png!
You're told that you need to get a new token.
(Repeat login in, copy/pasting token and trying to log in. Get the above)
In the Eclipse log you'll find the following for each failed attempt:
{code}
com.openshift.restclient.authorization.UnauthorizedException: "You must obtain an API token by visiting https://api.stg.openshift.com/oauth/token/request"
at com.openshift.internal.restclient.authorization.OpenShiftAuthorizationRedirectStrategy.isRedirected(OpenShiftAuthorizationRedirectStrategy.java:56)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:103)
at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:439)
at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:209)
at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:199)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:263)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:335)
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)
{code}
was:
# EXEC: use an existing connection to https://console.stg.openshift.com
# EXEC: in case you're using an existing connection: launch application wizard and pick your connection to stg and hit "Next"
# ASSERT: you're told to obtain an API token
# EXEC: hit "retrieve", log in, copy the token in the dialog and paste it into the form
# EXEC: hit "Next"
Result:
!cannot-login-stg.png!
You're told that you need to get a new token.
(Repeat login in, copy/pasting token and trying to log in. Get the above)
> Connection wizard: Cannot log into v3 STG
> -----------------------------------------
>
> Key: JBIDE-20289
> URL: https://issues.jboss.org/browse/JBIDE-20289
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Priority: Blocker
> Labels: connection_wizard
> Fix For: 4.3.0.Beta2
>
> Attachments: cannot-login-stg.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jbosstools-issues
mailing list