[
https://issues.jboss.org/browse/JBIDE-22806?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich updated JBIDE-22806:
------------------------------------------
Steps to Reproduce:
# ASSERT: have a server that lets you log in via oauth (ex.
https://console.engint.openshift.com)
# EXEC: launch connection wizard, choose openshift 3 type, provide server url and ensure
"OAuth" is selected as authentication means
# ASSERT: "Finish" is disabled
# EXEC: hit the "retrieve" link and wait for the oauth dialog to appear
# EXEC: close auth dialog (do NOT log in nor retrieve any token)
Result:
"Finish" is enabled, "Token" has no required marker
!connection-page-finish-enabled.png!
was:
# ASSERT: have a server that lets you log in via oauth (ex.
https://console.engint.openshift.com)
# EXEC: launch connection wizard, choose openshift 3 type, provide server url and ensure
"OAuth" is selected as authentication means
# ASSERT: "Finish" is enabled
# EXEC: hit the "retrieve" link and wait for the oauth dialog to appear
# EXEC: close auth dialog (do NOT log in nor retrieve any token)
Result:
"Finish" is enabled, "Token" has no required marker
!connection-page-finish-enabled.png!
Connection wizard: "Finish" is enabled even though I didnt
oauth authenticate to pick a token
---------------------------------------------------------------------------------------------
Key: JBIDE-22806
URL:
https://issues.jboss.org/browse/JBIDE-22806
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.1.AM2
Reporter: Andre Dietisheim
Priority: Minor
Fix For: 4.4.1.AM3
Attachments: connection-page-finish-enabled.png
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)