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

Connection wizard: cannot connect to console.stg.openshift.com

    XMLWordPrintable

Details

    • Sprint #4 May 2015
    • Hide
      1. EXEC: launch openshift connection wizard
      2. EXEC: as url use https://console.stg.openshift.com (or https://api.stg.openshift.com/ )
      3. EXEC: add some credentials
      4. EXEC: hit finish
      5. ASSERT: SSL certificate dialog pops up
      6. EXEC: confirm the certificate

      Result:

      You are told that the wizard cannot connect even though the server is reachable via browser:

      Expected result:
      I should be able to connect to console.stg.openshift.com

      Show
      EXEC: launch openshift connection wizard EXEC: as url use https://console.stg.openshift.com (or https://api.stg.openshift.com/ ) EXEC: add some credentials EXEC: hit finish ASSERT: SSL certificate dialog pops up EXEC: confirm the certificate Result: You are told that the wizard cannot connect even though the server is reachable via browser: Expected result: I should be able to connect to console.stg.openshift.com

    Attachments

      1. blank-browser-page.ogv
        929 kB
      2. retrieve-dialog-1.png
        retrieve-dialog-1.png
        74 kB
      3. retrieve-dialog-2.png
        retrieve-dialog-2.png
        4 kB
      4. unable-to-connect.png
        unable-to-connect.png
        44 kB
      5. webconsole.png
        webconsole.png
        61 kB

      Issue Links

        duplicates

        Bug - A problem that impairs or prevents the functions of the product. JBIDE-19935 Shell which is supposed to contain token for OAuth authentication for OpenShift v3 connection is empty.

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed
        is blocked by

        Feature Request - Feature requests from customers and/or users JBIDE-19829 Connection wizard: Add Oauth support

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed

        Feature Request - Feature requests from customers and/or users OSJC-170 Add User kind for v1beta1

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed
        is caused by

        Feature Request - Feature requests from customers and/or users JBIDE-19788 Connection wizard: As a user I want to connect to OpenShift v3 using oauth

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed

        Feature Request - Feature requests from customers and/or users OSJC-165 Allow OpenShiftRedirectionStrategy to determine the auth scheme

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed

        Feature Request - Feature requests from customers and/or users OSJC-166 Provide oauth based authentication

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed
        is related to

        Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-20105 Connection wizard: authenticate via OAuth in dialog (was: via external browser)

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed
        relates to

        Feature Request - Feature requests from customers and/or users JBIDE-19096 Connection wizard: Allow v2 and v3 Connections

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed

        Feature Request - Feature requests from customers and/or users JBIDE-19891 Replace OK/Cancel button with close

        • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
        • Closed

        Feature Request - Feature requests from customers and/or users JBIDE-19892 Move OAuth spinner page to external resource

        • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
        • Closed

        Activity

          People

            jcantril@redhat.com Jeffrey Cantrill
            adietish@redhat.com André Dietisheim
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: