[ https://issues.jboss.org/browse/JBIDE-11354?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11354: ------------------------------------- Fix Version/s: 3.3.0.Beta2 -- 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-11354?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11354: ------------------------------------- Steps to Reproduce: # EXEC: Open the Openshift view in eclipse # ASSERT: make sure you have a user-account on OpenShift that has no ssk-key yet (Web-GUI) # EXEC: Add this account (for which there is no pub ssh key on the server and no private key on the client) to the *OpenShift Express Console* # EXEC: Enter your username and password for the openshift account # You should now see the error above. was: Open the Openshift view in eclipse Try to add an account for which there is no pub ssh key on the server and no private key on the client Enter your username and password for the openshift account You should now see the error above. -- 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-11354?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-11354: ------------------------------------------ hum, very weird. I could not reproduce this (see my screencast openshift.ogv attached to this issue). There must be something more involved here. Any further instructions, please? -- 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-11354?page=com.atlassian.jira.plugi... ] Steven Pousty commented on JBIDE-11354: --------------------------------------- Hey Andre: I don't think we necessarily need to spend too much more time chasing down this issue if we fix the SSH key issues as a whole. In general, an eclipse user should be able to just load the plugin, go through the wizards (without touching SSH preferences), and get running. The other scenario we should support is that I have used the command line tools already and now I want to move that to eclipse. We should support that flow as well. Thanks Steve -- 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-11354?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-11354: ------------------------------------------ Hi Steven yes, you're right, it is crucial to have those 2 workflows functional. Thanks for reporting! {quote} In general, an eclipse user should be able to just load the plugin, go through the wizards (without touching SSH preferences), and get running. {quote} A problem in our domain wizard was preventing users from creating keys with it when there was no *.ssh* folder present yet. This is now fixed. The alternative path, where you'd create an ssh key in the SSH preferences is functional IMHO. I cannot reproduce what's being reported in JBIDE-11357. It only happens to me if you forget to manually add the key, that you created, in the OpenShift Web-UI. {quote} The other scenario we should support is that I have used the command line tools already and now I want to move that to eclipse. We should support that flow as well. {quote} This was imho always functional. The tricky parts are not to forget to add the key to the private keys in the Eclipse ssh preferences (which is adressed automatically if you use our wizard and NOT the SSH preferences) and to be careful to not comply to the key-name that is hardwired in the ssh-config OpenShift creates (.ssh/config): {code} Host *.rhcloud.com IdentityFile ~/.ssh/libra_id_rsa {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

[ https://issues.jboss.org/browse/JBIDE-11354?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-11354 at 3/22/12 9:03 AM: ------------------------------------------------------------------- Hi Steven yes, you're right, it is crucial to have those 2 workflows functional. Thanks for reporting! {quote} In general, an eclipse user should be able to just load the plugin, go through the wizards (without touching SSH preferences), and get running. {quote} A problem in our domain wizard was preventing users from creating keys with it when there was no *.ssh* folder present yet. This is now fixed. The alternative path, where you'd create an ssh key in the SSH preferences is functional IMHO. I cannot reproduce what's being reported in JBIDE-11357. It only happens to me if you forget to manually add the key, that you created, in the OpenShift Web-UI. {quote} The other scenario we should support is that I have used the command line tools already and now I want to move that to eclipse. We should support that flow as well. {quote} This was imho always functional. The tricky parts are to not forget to add the key to the private keys in the Eclipse ssh preferences (which is adressed automatically if you use our wizard and NOT the SSH preferences) and to be careful to not comply to the key-name that is hardwired in the ssh-config OpenShift creates (.ssh/config): {code} Host *.rhcloud.com IdentityFile ~/.ssh/libra_id_rsa {code} was (Author: adietish): Hi Steven yes, you're right, it is crucial to have those 2 workflows functional. Thanks for reporting! {quote} In general, an eclipse user should be able to just load the plugin, go through the wizards (without touching SSH preferences), and get running. {quote} A problem in our domain wizard was preventing users from creating keys with it when there was no *.ssh* folder present yet. This is now fixed. The alternative path, where you'd create an ssh key in the SSH preferences is functional IMHO. I cannot reproduce what's being reported in JBIDE-11357. It only happens to me if you forget to manually add the key, that you created, in the OpenShift Web-UI. {quote} The other scenario we should support is that I have used the command line tools already and now I want to move that to eclipse. We should support that flow as well. {quote} This was imho always functional. The tricky parts are not to forget to add the key to the private keys in the Eclipse ssh preferences (which is adressed automatically if you use our wizard and NOT the SSH preferences) and to be careful to not comply to the key-name that is hardwired in the ssh-config OpenShift creates (.ssh/config): {code} Host *.rhcloud.com IdentityFile ~/.ssh/libra_id_rsa {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

[ https://issues.jboss.org/browse/JBIDE-11354?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11354: ------------------------------------- Fix Version/s: 3.3.0.Beta2 (was: 3.3.0.Beta3) -- 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