Bug 1091407

Summary: Key authentication should be implemented in Remote Agent installation GUI page
Product: [Other] RHQ Project Reporter: Jeeva Kandasamy <jkandasa>
Component: Core UIAssignee: John Mazzitelli <mazz>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.11CC: hrupp, jshaughn
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: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Key authentication textbox is not available none

Description Jeeva Kandasamy 2014-04-25 14:10:31 UTC 
Created attachment 889772 [details]
Key authentication textbox is not available

Description of problem:
Key authentication should be implemented in Remote Agent installation GUI page, which is available via CLI

Version-Release number of selected component (if applicable):
Version : 4.11.0-SNAPSHOT
Build Number : 1bc9904
GWT Version : 2.5.0
SmartGWT Version : 3.0
Browser: Firefox 28

Steps to Reproduce:
1. Navigate to "Administration-->Agents-->New"
2. There is no text box to enter authentication key

Additional info: Screen shot is attached
Comment 1 John Mazzitelli 2014-04-29 19:58:27 UTC 
There are many questions that need to be answered in order to address this issue (nothing like this was in the requirements that I saw).

These are some of the major questions that I would think need to be answered. I think we should not schedule this for 4.11, because this could get out of hand with all the possibilities to implement. For example:

* Do we support having the user provide the private key bytes via the UI?
* Do we support having the user provide the path to the key file on the server? (and where is this file? how are they shared across RHQ Servers?)
* Do we support file upload of the key file?
* Do we support using encrypted keys/key files and thus the user must provide the passcode in the UI?
* Do we support a default key bytes (like we provide a default set of user/pass today) for use as a fallback if the user doesn't provide one in the UI?
* Do we support a default key file for use as a fallback if the user doesn't provide one in the UI?
** If we do support default key files, do we allow the user to file upload a default key file in the System Settings UI or do we just point to a file path (and if its the latter, how do we share them across RHQ Servers?)
* Do we support a default passcode for a default key if the default key (or keyfile) is encrypted?

So there is much to consider if we are to say "key authentication should be implemented."