Configure the Ansible Control Node.
All right,
so let's cast our mind back through all those many minutes to the beginning of
the course when we were discussing Ansible architecture.
Remember that, by definition, Ansible was built with agentlessness and mind.
So relying upon existing network protocols,
relying upon existing or easily obtainable client server stacks,
this sort of stuff.
Secure shell is the standard when you're using Linux, macOS.
It's in preview mode on Windows so you can experiment with it,
but be careful in production.
I'm assuming production,
so we're staying with the tried and true Windows Remote
Management or WinRM service that relies upon an older,
it's not a RESTful service that uses the SOAP and XML protocol and format,
respectively, but it's the old standard,
PowerShell remoting, using the Windows CIM,
or common information model, on accessing system configuration properties.
Kerberos is the native authentication protocol in
Active Directory domains. But of course,
Kerberos itself started in the UNIX world, and it's cross‑platform itself too.
It seems doubtful to me for a business to standardize on
Kerberos when you've got Linux servers. Well,
maybe if you have Linux desktops in place.
That's another discussion for another time.