Manage Root's SSH Keys should be laid out more like a wizard.
Right now, entering a SSH key for ROOT is a bit nebulous. Especially for inexperienced users.
For example, you can import both a public and private key from one screen wherein you probably only need to import one.
Ideally, clicking "Insert" should result in a question:
Do you wish to import a [] Public key [] Private key [] Both Public and Private keys
The page should then ask for only the relevant info. (ie: don't display a blank space for a public key if the user only wants to import a private key.)
Furthermore, the vague NOTE at the bottom:
"Note: You don't have to import both keys. It is perfectly acceptable to just
import a public OR private key if that is all you need on the server."
would be rendered useless. To a new user, they may be thinking "is that all I need on this server? Which one? I don't know..." (Who decides whether or not a PUBLIC or PRIVATE key is needed for this server? Even the tip is nebulous.)
Finally, once the key has been imported, the response of "The key named was imported.The key named was imported.Import failed: key file 4908411_server_1@cpanel.net_1399267125.pub already exists." is a WTF kind of experience.
The user is left wondering: "The key named WHAT was imported? The other key named WHAT was imported? Which one of those is my Public key and which one is my private? Also, if they were imported, then why did my import fail?"
(I was able to do this by attempting to re-import a key that had already been imported.)
Please fix these errors and strange vagueries.
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
Definitely agreed that the error/success pages are confusing at best for this particular feature and need some improvement.
However, I feel the particular design you've proposed for changing the procedure of adding keys makes the feature unnecessarily complex. For users with several keys to import, you've now added another step with a whole new page load just to ask a question that shows/hides 1 box maximum.
If the wizard would show/hide more elements, then it'd be worthwhile in my opinion. Either way, this doesn't mean the existing layout/steps are perfect and don't need consideration. I just wanted to pose the thought that adding another intermediary page may be a step back.
Overall, I agree the SSH Key feature does need some reconsideration. We've been chipping away at this in prior releases with features like the SSL management feature.
Definitely agreed that the error/success pages are confusing at best for this particular feature and need some improvement.
However, I feel the particular design you've proposed for changing the procedure of adding keys makes the feature unnecessarily complex. For users with several keys to import, you've now added another step with a whole new page load just to ask a question that shows/hides 1 box maximum.
If the wizard would show/hide more elements, then it'd be worthwhile in my opinion. Either way, this doesn't mean the existing layout/steps are perfect and don't need consideration. I just wanted to pose the thought that adding another intermediary page may be a step back.
Overall, I agree the SSH Key feature does need some reconsideration. We've been chipping away at this in prior releases with features like the SSL management feature.
Definitely agreed that the error/success pages are confusing at best for this particular feature and need some improvement.
However, I feel the particular design you've proposed for changing the procedure of adding keys makes the feature unnecessarily complex. For users with several keys to import, you've now added another step with a whole new page load just to ask a question that shows/hides 1 box maximum.
If the wizard would show/hide more elements, then it'd be worthwhile in my opinion. Either way, this doesn't mean the existing layout/steps are perfect and don't need consideration. I just wanted to pose the thought that adding another intermediary page may be a step back.
Overall, I agree the SSH Key feature does need some reconsideration. We've been chipping away at this in prior releases with features like the SSL management feature.
Definitely agreed that the error/success pages are confusing at best for this particular feature and need some improvement.
However, I feel the particular design you've proposed for changing the procedure of adding keys makes the feature unnecessarily complex. For users with several keys to import, you've now added another step with a whole new page load just to ask a question that shows/hides 1 box maximum.
If the wizard would show/hide more elements, then it'd be worthwhile in my opinion. Either way, this doesn't mean the existing layout/steps are perfect and don't need consideration. I just wanted to pose the thought that adding another intermediary page may be a step back.
Overall, I agree the SSH Key feature does need some reconsideration. We've been chipping away at this in prior releases with features like the SSL management feature.
Ok... Valid point... Include in the first page of the "wizard" the question: "How many keys do you need to import? [1]" and go up from there. That would solve a myriad of problems in that, if someone had to add 12 private keys, they could just as easily answer that one question (once), and be presented a screen with the 12 private key boxes. (Assuming you add one per field, and can't just lump them all together in one box... I rarely do this sort of thing...)
Ok... Valid point... Include in the first page of the "wizard" the question: "How many keys do you need to import? [1]" and go up from there. That would solve a myriad of problems in that, if someone had to add 12 private keys, they could just as easily answer that one question (once), and be presented a screen with the 12 private key boxes. (Assuming you add one per field, and can't just lump them all together in one box... I rarely do this sort of thing...)
Replies have been locked on this page!