[jbosstools-issues] [JBoss JIRA] (JBIDE-20596) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box

[Marián Labuda (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-20596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marián Labuda updated JBIDE-20596:
----------------------------------
        Steps to Reproduce: 
ASSERT: There is no OpenShift connection.
EXEC: Open New OpenShift Application wizard via JBoss Central
EXEC: Select OpenShift 3 server type and OAuth authentication method.
EXEC: Enter any token into a token field - it must be pasted, not typed.

RESULT: Next button is disabled.
EXPECTED RESULT: Next button is enabled
    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, paste it. Or remove last character and type it again, then the Next button gets enabled.
                Workaround: Workaround Exists


> 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)