[
https://issues.jboss.org/browse/JBIDE-11912?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11912:
---------------------------------------------
Move buttons for list editing to a column on the right.
Put name used as comment of the generated key.
Show SSH2 home as browsable, then two fields for public and private key file name with
defaults based on what type it is: id_rsa / id_rsa.pub and id_dsa / id_dsa.pub
No need to show generated content, just make sure the files can be saved, enable the
finish button, if no passphrase ask user if he wants that (use same text as from eclipse
SSH dialog) and then save and upload on finish.
Improve SSH key management
--------------------------
Key: JBIDE-11912
URL:
https://issues.jboss.org/browse/JBIDE-11912
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 3.3.0.CR1
Reporter: Andre Dietisheim
Assignee: Max Rydahl Andersen
Labels: new_and_noteworthy
Fix For: 4.0.0.Alpha2
Attachments: 2012-09-04 17.24.bmml, 2012-09-04 17.24.png, create-domain.png
Initially OpenShift was only able to handle a single unique SSH (rsa) key. A user also
had to provide his key when creating the domain.
Things evolved a lot since then. The current OpenShift release supports
- multiple keys
- rsa and dsa keys
- keys are not required when creating a domain
Our tooling still offers what we implemented when OpenShift required one to provide his
single key when creating the domain. We require the user to create/provide his key when he
wants to create his domain.
!create-domain.png!
Furthermore we also force the key-name to libra_id_rsa. We did that to avoid conflicts
with the config (<home>/.ssh/config) that the rhc CLI tools create.
--
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