Loading...

XML

Word

Printable

Sprint:
Sprint #4 May 2015
Steps to Reproduce:
Hide

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
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
Git Pull Request:
https://github.com/jbosstools/jbosstools-openshift/pull/649

duplicates

JBIDE-19935 Shell which is supposed to contain token for OAuth authentication for OpenShift v3 connection is empty.

is blocked by

JBIDE-19829 Connection wizard: Add Oauth support

OSJC-170 Add User kind for v1beta1

is caused by

JBIDE-19788 Connection wizard: As a user I want to connect to OpenShift v3 using oauth

OSJC-165 Allow OpenShiftRedirectionStrategy to determine the auth scheme

OSJC-166 Provide oauth based authentication

is related to

JBIDE-20105 Connection wizard: authenticate via OAuth in dialog (was: via external browser)

relates to

JBIDE-19096 Connection wizard: Allow v2 and v3 Connections

JBIDE-19891 Replace OK/Cancel button with close

JBIDE-19892 Move OAuth spinner page to external resource

(1 is caused by, 1 is related to, 3 relates to)