Description of problem: In MTV-2.3 web console, in Add provider window this fingerprint is fetched automatically in UI. In MTV-2.2 users were expected to fetch it. According to this change Please update MTV-2.3 doc as follows: 1) Remove: Section: “2.6.2. Obtaining the SHA-1 fingerprint of a vCenter host” This command is mentioned: $ openssl s_client \ -connect <www.example.com>:443 \ < /dev/null 2>/dev/null \ | openssl x509 -fingerprint -noout -in /dev/stdin \ | cut -d '=' -f 2 2) In section: "4.1.1. Adding a VMware source provider" the "vCenter SHA-1 fingerprint." Prerequisite can be removed. Version-Release number of selected component (if applicable): MTV-2.2 Additional info: This change is for MTV-2.3+ Document.
@istein Should the whole section on obtaining the SHA-1 fingerprint be removed?
Sasha, I think we need to document what's in the new "Add provider" in MTV-2.3. Instead of asking for Fingerprint, the user is asked to verify the certificate. Please see the last 2 "Add provider" screenshots for reference.
Ilanit, Should I make these changes within the scope of this bug? And my initial question still stands - looks like the whole section on obtaining the SHA-1 fingerprint is not needed anymore. Is it correct?
In the scope of this bug these changes are required: "4.1.1. Adding a VMware source provider" section needs to change as follows: - Remove prerequisite: vCenter SHA-1 fingerprint. - In the procedure, need to change: from: SHA-1 fingerprint: vCenter SHA-1 fingerprint To: click the "I trust the authenticity of this certificate" (Check attached "Add VMware provider second screenshot " to see how it looks like in MTV-2.3). In section "5.1. Migrating virtual machines" Procedure, Step 2 about creating the secret: <vcenter_fingerprint> is required. Therefore we still need to keep in MTV-2.3 document this section: "2.6.2. Obtaining the SHA-1 fingerprint of a vCenter host"
Hi Ilanit, You wrote: - In the procedure, need to change: from: SHA-1 fingerprint: vCenter SHA-1 fingerprint To: click the "I trust the authenticity of this certificate" Do I understand correctly that first the user should click 'Verify certificate'? Another question: In section Migrating virtual machines, should obtaining the SHA-1 fingerprint of a vCenter host be added as a VMware-only prerequisite?
PR: https://github.com/konveyor/forklift-documentation/pull/287 Ready for QE review
In reply to comment #8: Do I understand correctly that first the user should click 'Verify certificate'? >Yes In section Migrating virtual machines, should obtaining the SHA-1 fingerprint of a vCenter host be added as a VMware-only prerequisite? This prerequisite is VMware only, and also only if the VMware provider is added via CLI.
Moving to Verified as the PR mentioned in comment #9 looks good.