We have converted most of our playbooks to use client cert based auth and have scheduled them in tower where a single client certificate exists. When ever we want to run the playbooks manually for testing or devlopment outside of tower we want the ability to easily switch to username/password.
I would like to propose allow both username/password as well as client certificate cert and key path authentication fields to netapp.ontap modules. If one of the fields is empty, then default to using the other. If both basic and client cert auth fields exists and are correctly populated default to using client cert based authentication.
Summary
We have converted most of our playbooks to use client cert based auth and have scheduled them in tower where a single client certificate exists. When ever we want to run the playbooks manually for testing or devlopment outside of tower we want the ability to easily switch to username/password.
I would like to propose allow both username/password as well as client certificate cert and key path authentication fields to netapp.ontap modules. If one of the fields is empty, then default to using the other. If both basic and client cert auth fields exists and are correctly populated default to using client cert based authentication.
Component Name
netapp.ontap
Additional Information