[jbosstools-issues] [JBoss JIRA] (JBIDE-12016) OpenShift Wizard should warn if domain exists but there's no ssh key on local machine (domain was created in web ui)
[
https://issues.jboss.org/browse/JBIDE-12016?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-12016:
------------------------------------------
Since the above code snippets did not unveil any encryption check as I had expected I
suggest we provide simple public key checks/comparisons.
We could look up existing private keys on the local machine (Eclipse preferences /
.ssh-directory) and guess the public keys for them by adding ".pub" to the name.
We could then try to load them and compare them to the keys registered in OpenShift.
Instead of guessing public key file names, we could also generate the public key for the
given private keys - since there's always 1 single public key for a private key. The
drawback is that we'd trigger secure storage password dialog or would have to ask the
user to provide the private key passphrase(s). This seem very annoying/unexpected in a
wizard whose purpose is just to import/create an OpenShift application. We could
eventually do that verification only if the user hits a "Verify..." button
(pretty much as you verify the credentials when defining a new SVN server).
OpenShift Wizard should warn if domain exists but there's no ssh
key on local machine (domain was created in web ui)
--------------------------------------------------------------------------------------------------------------------
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: 4.0.0.Alpha2
Attachments: cloning-settings.png, 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.
How to reproduce:
1. ASSERT: make sure you have an OpenShift user without a domain (create a new user or
kill your users domain)
2. EXEC: launch *OpenShift Application* wizard and create a new application
Result:
Cloning fails, since there are no ssh-keys on the local machine and no keys were added to
OpenShift. The wizard did not tell the user since the domain already existed. The domain
creation dialog is currently the only place that would allow a user to create a new
ssh-key. If you already have a domain, you'll never get asked to create your keys.
--
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