[ https://issues.jboss.org/browse/JBIDE-11810?page=com.atlassian.jira.plugi... ] Stefan Bunciak updated JBIDE-11810: ----------------------------------- Description: Stack trace: {code} com.jcraft.jsch.JSchException: Auth fail at com.jcraft.jsch.Session.connect(Session.java:461) at com.jcraft.jsch.Session.connect(Session.java:154) at org.jboss.tools.openshift.express.internal.ui.utils.OpenShiftSshSessionFactory.createSession(OpenShiftSshSessionFactory.java:105) at org.jboss.tools.openshift.express.internal.ui.utils.OpenShiftSshSessionFactory.createSession(OpenShiftSshSessionFactory.java:82) at org.jboss.tools.openshift.express.internal.core.portforward.ApplicationPortForwardingWizardPage.verifyApplicationSSHSession(ApplicationPortForwardingWizardPage.java:364) at org.jboss.tools.openshift.express.internal.core.portforward.ApplicationPortForwardingWizardPage.access$1(ApplicationPortForwardingWizardPage.java:360) at org.jboss.tools.openshift.express.internal.core.portforward.ApplicationPortForwardingWizardPage$4$1.run(ApplicationPortForwardingWizardPage.java:194) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} Steps to Reproduce: * ASSERT: Have at least one application on OpenShift * ASSERT: Do *not* have private portion of the OpenShift ssh key added to the ssh preferences * EXEC: Create a new OpenShift connection via OpenShift Explorer * EXEC: Collapse the newly created account * EXEC: Right click on it and open the Port forwarding dialog * RESULT: !machydraerrorportdialog.png|thumbmail! * EXPECT: Create some security guard, like discussed in [JBIDE-11535|https://issues.jboss.org/browse/JBIDE-11535?focusedCommentId=...] to prevent such auth failures/situations. was: * ASSERT: Have at least one application on OpenShift * ASSERT: Do *not* have private portion of the OpenShift ssh key added to the ssh preferences * EXEC: Create a new OpenShift connection via OpenShift Explorer * EXEC: Collapse the newly created account * EXEC: Right click on it and open the Port forwarding dialog * RESULT: !machydraerrorportdialog.png|thumbmail! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11810?page=com.atlassian.jira.plugi... ] Stefan Bunciak commented on JBIDE-11810: ---------------------------------------- Maybe a good compromise would be to establish ssh connection at the credentials verification phase. If it's successfully established then terminate it. After this verification a good error handling should be enough. WDYT? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11810?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-11810: ---------------------------------- Attachment: Screen Shot 2012-05-22 at 3.23.01 PM.png Screenshot of the error that is reported to the user when he opens the port-forwarding dialog without ssh key configured. Also, the port-forwarding dialog itself does not appear, avoiding other errors due to 'null' ssh session. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11810?page=com.atlassian.jira.plugi... ] Stefan Bunciak closed JBIDE-11810. ---------------------------------- Closing on behalf of opening a new issue JBIDE-12118. Verified in JBoss Developer Studio Version: 5.0.0.CR1 Build id: v20120605-2229-H183-CR1 Build date: 20120605-2229 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira