[ https://issues.jboss.org/browse/JBIDE-21325?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21325: ------------------------------------- Steps to Reproduce: # ASSERT: have connection with stored token ("Save token (could trigger secure storage login)" # ASSERT: have oc binary available in cmd line # EXEC: using *oc* in cmd line, login with the very same token that you're using in Eclipse (oc login --token=XXXX) and logout (this will expire your token) # EXEC: in Servers view context menu: New > Server # ASSERT: connection dialog shows up # EXEC: pick your connection (with the stored token) and hit Next Result: a 2nd, nested connection dialog shows up. !nested-2nd-conncetion-dialog.png! The very same can be achieved by using an invalid token. A 2nd dialog pops up. was: # ASSERT: have connection with stored token ("Save token (could trigger secure storage login)" # ASSERT: have oc binary available in cmd line # EXEC: using *oc* in cmd line, login with the very same token that you're using in Eclipse (oc login --token=XXXX) and logout (this will expire your token) # EXEC: in Servers view context menu: New > Server # ASSERT: connection dialog shows up # EXEC: pick your connection (with the stored token) and hit Next Result: a 2nd, nested connection dialog shows up. !nested-2nd-conncetion-dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)