[jbosstools-issues] [JBoss JIRA] (JBIDE-12016) OpenShift Wizard should warn if there are no private keys on local machine that match the public keys on OpenShift

Andre Dietisheim (JIRA) jira-events at lists.jboss.org
Wed Jan 9 13:45:09 EST 2013


     [ https://issues.jboss.org/browse/JBIDE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-12016:
-------------------------------------

    Priority: Minor  (was: Major)

    
> OpenShift Wizard should warn if there are no private keys on local machine that match the public keys on OpenShift 
> -------------------------------------------------------------------------------------------------------------------
>
>                 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, 3.3.0.Final
>            Reporter: Burr Sutter
>            Assignee: Andre Dietisheim
>            Priority: Minor
>             Fix For: LATER
>
>         Attachments: cloning-settings.png, creating-domain.png, manage-ssh-keys.png, no-keys.png, Screen Shot 2012-05-25 at 10.57.18 AM.png
>
>
> How to reproduce:
> # ASSERT: make sure you have an account with at least 1 public key on OpenShift
> # ASSERT: make sure you have the private key for this private key registered to your SSH2 preferences in Eclipse
> # EXEC: launch *New OpenShift Application* wizard
> # EXEC: on the last page (git cloning settings), hit the SSH2 Preferences link and remove your private key from the list of private keys
> # ASSERT: back on the git cloning wizard page you're not warned that there's no private key that would match the private keys on your machine
> # EXEC: hit *Finish*
> Result:
> Cloning  fails since you have no private key registered to the Eclipse SSH2 preferences that would allow you to clone from OpenShift.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list