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

Connection wizard: switching to <New Connection> resets token but form is still valid

XMLWordPrintable

    • Hide
      1. ASSERT: make sure you have at least 1 (existing) connection listed in the explorer
      2. ASSERT: have a freshly launched Eclipse
      3. EXEC: launch app wizard via link in central (or File->New->OpenShift)
      4. ASSERT: your existing connection is preselected and username/pw (or token for a OpenShift v3 connection) are filled with values
      5. EXEC: Switch connection combobox to <New Connection>

      Result:
      In case of OpenShift v2 username and password are blank, but not decorated with a "*" marking it as required. The "Next" button is therefore enabled.
      In case of OpenShift v3 the server url is now blank and decorated with a "*" marking it as required. Username/Password or Token are blank but not marked as required.

      Expected result:
      authentication details are blank but marked as required, "Next" is disabled.

      Show
      ASSERT: make sure you have at least 1 (existing) connection listed in the explorer ASSERT: have a freshly launched Eclipse EXEC: launch app wizard via link in central (or File->New->OpenShift) ASSERT: your existing connection is preselected and username/pw (or token for a OpenShift v3 connection) are filled with values EXEC: Switch connection combobox to <New Connection> Result: In case of OpenShift v2 username and password are blank, but not decorated with a "*" marking it as required. The "Next" button is therefore enabled. In case of OpenShift v3 the server url is now blank and decorated with a "*" marking it as required. Username/Password or Token are blank but not marked as required. Expected result: authentication details are blank but marked as required, "Next" is disabled.

            adietish@redhat.com André Dietisheim
            adietish@redhat.com André Dietisheim
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: