[
https://issues.jboss.org/browse/JBIDE-20596?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-20596:
-------------------------------------
Workaround Description:
There are several ways to workaround this issues:
a) Check and uncheck checkbox for a default server usage
b) Switch to Basic authentication method and then switch to OAuth again - because token is
cached, the Next button gets enabled.
c) Instead of pasting token, type it. Or remove last character and type it again or
check&uncheck "Save Token".
-> then the Next button gets enabled.
was:
There are several ways to workaround this issues:
a) Check and uncheck checkbox for a default server usage
b) Switch to Basic authentication method and then switch to OAuth again - because token is
cached, the Next button gets enabled.
c) Instead of pasting token, type it. Or remove last character and type it again, then the
Next button gets enabled.
Next button in the New OpenShift Application window is enabled only
after clicking Use default server check box
---------------------------------------------------------------------------------------------------------------
Key: JBIDE-20596
URL:
https://issues.jboss.org/browse/JBIDE-20596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Supriya Bharadwaj
Assignee: Jeff Cantrill
Fix For: 4.3.1.Beta1
Attachments: screenshot-1.png, screenshot-2.png
In the New OpenShift Application window, after all the fields are filled in and the token
is entered in the Token field, (my guess is) the Next button should get enabled, which
doesn't happen. The button gets enabled only after the "Use default Server"
check box is clicked. Is this a bug?
(I am trying this in JBDS v9.0cr1)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)