doc: describe how to use certificate authentication for the StatPerf …

[cgrinds]

…collector

Thanks to Esteban for reporting!

[Copilot]

Pull request overview

Updates the ONTAP cluster preparation documentation to include guidance for using non-password authentication when configuring the StatPerf collector.

Changes:

• Adds additional security login create commands intended for certificate-based authentication for StatPerf.
• Introduces an SSH publickey login entry alongside the existing password-based SSH/HTTP entries in the StatPerf least-privilege section.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This section says “certificate authentication” but the added SSH command uses -authentication-method publickey (SSH key auth), and StatPerf itself calls the REST private CLI endpoint (api/private/cli) rather than using SSH. To avoid misleading readers, either (a) remove the SSH publickey login if it’s not required for StatPerf, or (b) explain why an SSH login is still needed for authorization and reword the comment to distinguish SSH key auth from HTTP client-certificate auth. Also consider mirroring the earlier pattern used in this doc (“Use this for password auth” vs “Or this for certificate auth”) instead of “run these commands as well,” which reads like both are required.

Suggested change

	# If you also want to use certificate authentication for the StatPerf collector, run these commands as well
	security login create -user-or-group-name harvest2 -application ssh -authentication-method publickey -role harvest2-role
	# Or, if you want to use HTTP client-certificate authentication for the StatPerf collector: