VMware hosts may be configured with an SSH key pair for remote login. The ssh_keypair authentication type exists in CloudForms. Enabling it for the VMware hosts would extend the connection capabilities.
@Fabien what do you mean by "Enabling it for the VMware hosts would extend the connection capabilities." ? The backend is flexible, you can add an SSH key to any host if you want: >> host = ManageIQ::Providers::Vmware::InfraManager::HostEsx.first >> host.update_authentication(:remote => {:auth_key => "ssh-rsa [snip] agrare", :userid => "agrare.com"}) >> host.authentication_check(:remote) => [false, "Login failed due to a bad username or password."] # Note I didn't actually add my ssh key but it really did check Or do you mean add the ability to add an ssh key from the UI? If so this sounds like a UI RFE not a providers RFE.
You're right. I mean from the UI, as it's the most common interaction. Will change the component.
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition. If it's something like a tracker bug where it doesn't matter, please set the severity to Low.
What is the current remote auth type ? Isn't it already SSH ? IIUC, the choice is between password and auth_key, rather than protocol.
Yes, the remote is already SSH already.
My understanding is that the names of the authentications are more "purposes". The protocol will vary: - remote : SSH with userid/password - remote with key: SSH with userid/private key - IPMI: IPMI with userid/password We could imagine more purposes, like: - ansible: SSH with userid/password - ansible escalated: SSH with userid/password and escalation parameters - SSA: VDDK with userid/password
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days