Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-20975

Next button in the New OpenShift Application window is enabled only after clicking Use default server check box

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.4.0.Alpha1
    • None
    • openshift
    • None
    • Hide

      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

      Show
      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 Exists
    • Hide

      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.

      Show
      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.

      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)

        1. screenshot-1.png
          screenshot-1.png
          68 kB
        2. screenshot-2.png
          screenshot-2.png
          65 kB

              adietish@redhat.com André Dietisheim
              sbharadw@redhat.com Supriya Takkhi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: