[jbosstools-issues] [JBoss JIRA] (JBIDE-11810) OpenShift port forwarding exception without ssh key
Stefan Bunciak (JIRA)
jira-events at lists.jboss.org
Wed May 9 11:49:17 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-11810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12691483#comment-12691483 ]
Stefan Bunciak commented on JBIDE-11810:
----------------------------------------
I don't know how JBIDE-11222 is going to be resolved but if we keep one ssh connection (for the currently logged user) it would solve many auth problems I think.
> OpenShift port forwarding exception without ssh key
> ---------------------------------------------------
>
> Key: JBIDE-11810
> URL: https://issues.jboss.org/browse/JBIDE-11810
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Stefan Bunciak
> Assignee: Stefan Bunciak
> Priority: Critical
> Fix For: 3.3.0.CR1
>
> Attachments: machydraerrorportdialog.png
>
>
> 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}
--
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
More information about the jbosstools-issues
mailing list