37 lines
1.6 KiB
Markdown
37 lines
1.6 KiB
Markdown
---
|
|
sidebar_position: 1
|
|
---
|
|
# AWX Credential Types
|
|
When interacting with devices via Ansible Playbooks, you need to provide the playbook with credentials to connect to the device with. Examples are domain credentials for Windows devices, and local sudo user credentials for Linux.
|
|
|
|
## Windows-based Credentials
|
|
### NTLM
|
|
NTLM-based authentication is not exactly the most secure method of remotely running playbooks on Windows devices, but it is still encrypted using SSL certificates created by the device itself when provisioned correctly to enable WinRM functionality.
|
|
```jsx title="(NTLM) nicole.rappe@MOONGATE.LOCAL"
|
|
Credential Type: Machine
|
|
Username: nicole.rappe@MOONGATE.LOCAL
|
|
Password: <Encrypted>
|
|
Privilege Escalation Method: runas
|
|
Privilege Escalation Username: nicole.rappe@MOONGATE.LOCAL
|
|
```
|
|
### Kerberos
|
|
Kerberos-based authentication is generally considered the most secure method of authentication with Windows devices, but can be trickier to set up since it requires additional setup inside of AWX in the cluster for it to function properly. At this time, there is no working Kerberos documentation.
|
|
```jsx title="(Kerberos WinRM) nicole.rappe"
|
|
Credential Type: Kerberos WinRM
|
|
Username: nicole.rappe
|
|
Password: <Encrypted>
|
|
Kerberos Realm (Domain): MOONGATE.LOCAL
|
|
```
|
|
## Linux-based Credentials
|
|
```jsx title="(LINUX) nicole"
|
|
Credential Type: Machine
|
|
Username: nicole
|
|
Password: <Encrypted>
|
|
Privilege Escalation Method: sudo
|
|
Privilege Escalation Username: root
|
|
```
|
|
|
|
:::note
|
|
`WinRM / Kerberos` based credentials do not currently work as-expected. At this time, use either `Linux` or `NTLM` based credentials.
|
|
:::
|