[
https://issues.jboss.org/browse/JBIDE-11912?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-11912:
-------------------------------------
Release Notes Text: We now allow the user to manage the SSH public keys on OpenShift.
He's able to create and upload new keys but also to remove existing keys. The SSH keys
wizard is available in the context-menu of the OpenShift Explorer. The user may also get
to it when he's creating/importing an OpenShift application. The page dedicated to the
git cloning settings holds a link to the SSH preferences and the SSH keys wizard.
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: Andre Dietisheim
Labels: new_and_noteworthy
Fix For: 4.0.0.Alpha2
Attachments: 2012-09-04 17.24.bmml, 2012-09-04 17.24.bmml, 2012-09-04 17.24.bmml,
2012-09-04 17.24.bmml, 2012-09-04 17.24.png, add-existing-key.png, add-new-key.png,
create-domain.png, manage-ssh-keys-wizard.png, manage-ssh-keys.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