Bug 794476

Summary:	Getting invalid key name: libra_id_rsa
Product:	OKD	Reporter:	Nam Duong <nduong>
Component:	Website	Assignee:	Abhishek Gupta <abhgupta>
Status:	CLOSED DUPLICATE	QA Contact:	libra bugs <libra-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.x	CC:	abhgupta, jofernan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-18 01:20:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Nam Duong 2012-02-16 22:32:28 UTC

Description of problem:
On the control panel, if the user uses the same key name as found in their .ssh/ dir (libra_id_rsa), and add their public key, they get an error:  "Invalid key name: libra_id_rsa".  But a key named "libra" works.  

This is building a bit of frustration for our users while trying to work around permission denied issues on git/ssh commands.  A question I get from our users is "Why can't we allow underscores (or any chars for that matter)?  Its the same name as you assign it on my client".  And "Why isn't the error message clearer if its alphanumeric chars only?"  

Ideally, we should accept any name, especially one that we assign on key creation.  Please help them out.

Comment 1 Abhishek Gupta 2012-02-17 17:43:37 UTC

Note to triage team: 
There is a separate bug (Bug 794506) that deals with lifting some of these restrictions in the name of the keys. This particular bug would be addressed once we fix that one and as such could even be marked as a duplicate.

Comment 2 Abhishek Gupta 2012-02-18 01:20:44 UTC


*** This bug has been marked as a duplicate of bug 794506 ***