[
https://issues.jboss.org/browse/JBIDE-12016?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-12016:
------------------------------------------
In the latest OpenShift tooling creating the domain and ssh keys are split into separate
wizards:
!creating-domain.png!
!manage-ssh-keys.png!
It does therefore not matter any more, if you created your domain in the web-UI or in
JBT/JBDS. To make sure that the user added keys to his OpenShift account, we now error in
the OpenShift Application creation wizard, if there are no keys on OpenShift yet (and
provide a link to the kes wizard):
!no-keys.png!
We cannot check if a local private key would match the public keys on OpenShift thoug. The
comments above show that we have to either patch JSch or use the bouncycastle crypto
library. Eclipse is currently validating bouncycastle and will provide it in upcoming
egit-releases:
https://t.co/OEXpP0V0
https://t.co/XdYr9l3V
I therefore updated the title of this issue to match the requirement that's still
missing: warn if there are no private key on the local machine that match the public keys
on OpenShift.
I moved the initial usecase, where we wanted to prevent the user from cloning if he had
not added keys to OpenShift yet: JBIDE-12655
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
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