[jbosstools-issues] [JBoss JIRA] (JBIDE-11354) Adding a OpenShift account fails if there is no SSH key

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-11354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678637#comment-12678637 ] 

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}

                
> Adding a OpenShift account fails if there is no SSH key
> -------------------------------------------------------
>
>                 Key: JBIDE-11354
>                 URL: https://issues.jboss.org/browse/JBIDE-11354
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 3.3.0.Beta1
>            Reporter: Steven Pousty
>            Assignee: Andre Dietisheim
>             Fix For: 3.3.0.Beta3
>
>         Attachments: openshift.ogv
>
>
> When I try to add a new Account to the OpenShift view, if there is no SSH key I get the following error after putting in the username and password and pressing next
> Could not check user credentials: Could not unmarshall response "{"api_c":["placeholder"],"broker_c":["namespace","rhlogin","ssh","app_uuid","debug","alter","cartridge","cart_type","action","app_name","api"],"api":"1.1.2","exit_code":0,"result":"","messages":"","debug":"","data":{"user_info":{"rhlogin":"spousty+mongo at redhat.com","uuid":"8e863f72f2f743b58003257077d700dd","rhc_domain":"rhcloud.com","vip":false,"ssh_type":"","max_gears":5,"ssh_keys":{},"ssh_key":"","consumed_gears":0,"namespace":"spousty0mongo"},"app_info":{}}}".
> It is caused by there not being an SSH key in place for that account. 
> We should either allow the user to specify a SSH key or give a better error message.
> 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