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

[Steven Pousty (JIRA)]

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

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
                
> 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.Beta2
>
>         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