[ https://issues.jboss.org/browse/JBIDE-9923?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-9923: ------------------------------------ Steps to Reproduce: 1.) ASSERT: have an OpenShift Domain and an Application 2.) EXECUTE: remove the private ssh key - the private portion of the ssh key, that you used when creating your domain - from the SSH2 preferences (Preferences->General->Network Connections->SSH2->Private keys) 3.) EXECUTE: restart Eclipse 4.) EXECUTE: launch the OpenShift Application wizard 5.) EXECUTE: select an application, get to the last page and hit "Finish" 6.) EXECUTE: see that the clone fails with the following error: !auth-error.png! 7.) EXECUTE: add your private key (back) to the ssh preferences 8.) EXECUTE: try to import the OpenShift application again Result: The import still fails with the very same authentication error was: # ASSERT: have an OpenShift Domain and an Application # EXECUTE: remove the private ssh key - the private portion of the ssh key, that you used when creating your domain - from the SSH2 preferences (Preferences->General->Network Connections->SSH2->Private keys) # EXECUTE: restart Eclipse # EXECUTE: launch the OpenShift Application wizard #EXECUTE: select an application, get to the last page and hit "Finish" #EXECUTE: see that the clone fails with the following error: !auth-error.png! # EXECUTE: add your private key (back) to the ssh preferences # EXECUTE: try to import the OpenShift application again Result: The import still fails with the very same authentication error -- 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-9923?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-9923: ----------------------------------------- The root cause is that the key are initialized when the EGit UI plugin is started. The responsible component, the SshSessionFactory is initialized once per eclipse session and not refreshed (even if you change the ssh preferences). @see org.eclipse.egit.ui.Activator#setupSSH @see SshSessionFactory#setInstance @see EclipseSshSessionFactory It should be no problem to fix this since changes in the preferences may be listened to. -- 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-9923?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-9923: ------------------------------------ Steps to Reproduce: 1.) ASSERT: have an OpenShift Domain and an Application 2.) EXECUTE: remove the private ssh key - the private portion of the ssh key, that you used when creating your domain - from the SSH2 preferences (Preferences->General->Network Connections->SSH2->Private keys) 3.) EXECUTE: restart Eclipse (MANDATORY!) 4.) EXECUTE: launch the OpenShift Application wizard 5.) EXECUTE: select an application, get to the last page and hit "Finish" 6.) EXECUTE: see that the clone fails with the following error: !auth-error.png! 7.) EXECUTE: add your private key (back) to the ssh preferences 8.) EXECUTE: try to import the OpenShift application again Result: The import still fails with the very same authentication error The opposite shows a consitent behaviour: Remove your ssh-key once you could import your app and try to clone another app. It still works. was: 1.) ASSERT: have an OpenShift Domain and an Application 2.) EXECUTE: remove the private ssh key - the private portion of the ssh key, that you used when creating your domain - from the SSH2 preferences (Preferences->General->Network Connections->SSH2->Private keys) 3.) EXECUTE: restart Eclipse 4.) EXECUTE: launch the OpenShift Application wizard 5.) EXECUTE: select an application, get to the last page and hit "Finish" 6.) EXECUTE: see that the clone fails with the following error: !auth-error.png! 7.) EXECUTE: add your private key (back) to the ssh preferences 8.) EXECUTE: try to import the OpenShift application again Result: The import still fails with the very same authentication error -- 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-9923?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-9923: ------------------------------------ Fix Version/s: 3.3.0.CR1 (was: 3.3.0.Beta1) -- 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-9923?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen resolved JBIDE-9923. ---------------------------------------- Resolution: Cannot Reproduce Bug Known issues are: If your ssh directory is not named correctly (especially on windows) there could be problems. Solution: set the right directory in preferences. Your key is wrong - solution: add the right key. Your key has the wrong permissions - solution: we now create keys with right permissions and in case you have used plain eclipse key creation or something else that sets the permissons wrong then run chmod 700 yourkey and ensure it is added. You have a ~/.ssh/config that hardwires the key to use for a specific domain. solution: remove your ~/.ssh/config or adjust it to use the right key. Thus at this moment we do not know of anything that requires a restart of eclipse to work. -- 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