[jbosstools-issues] [JBoss JIRA] (JBIDE-12016) OpenShift Wizard - SSH2 Preferences

Fri May 25 18:51:18 EDT 2012

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

Andre Dietisheim edited comment on JBIDE-12016 at 5/25/12 6:51 PM:
-------------------------------------------------------------------

@Burr what I dont get here is how people got so far without having a key. If you're new to openshift you have no domain and the tooling will ask you to create a domain and a key first. It'll register the key to the prefs and you'd be completey setup (key, prefs all done). I assume the class created the domain in the web-ui then?

      was (Author: adietish):
    @Burr what I dont get here is how people got so far without having a key. If you're new to openshift you have no domain and the tooling will ask you to create a domain and a key first. I assume the class created the domain in the web-ui then?

> OpenShift Wizard - SSH2 Preferences
> -----------------------------------
>
>                 Key: JBIDE-12016
>                 URL: https://issues.jboss.org/browse/JBIDE-12016
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>    Affects Versions: 3.3.0.Beta3
>            Reporter: Burr Sutter
>            Assignee: Andre Dietisheim
>             Fix For: 3.4.x
>
>         Attachments: Screen Shot 2012-05-25 at 10.57.18 AM.png
>
>
> If the end-user's .ssh directory is empty - we should provide a stronger warning for them - ideally provide a URL to some documentation/video explaining how the user can use Eclipse/JBoss Tools to create their private/public keys - so they can then upload the .pub to OpenShift.
> At least 10 users failed this test today and had to be "handheld" through the process.   
> What is worse, if the end-user uploads a slightly butchered pub key - the create application phase still works but the git clone fails - with a relatively poor error message - recovery normally means having to go up to the OpenShift console, deleting the poorly created apps - getting the pub key uploaded correctly (deleting the previous one) and starting again.
> The fact that Eclipse could create the keys was actually unknown by the instructor's of today's class.  SSH is still a nightmare for the newbie trying to use OpenShift + JBDS.

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