Restructured Documentation
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 8s

This commit is contained in:
2026-09-05 14:08:43 -06:00
parent c4bd235eba
commit 289769a601
281 changed files with 5403 additions and 3563 deletions
@@ -0,0 +1,48 @@
---
tags:
- Ansible
- Automation
---
## Purpose
Record AWX credential examples for Linux and Windows targets. The examples retain their original domain context and must be reconciled with the authentication method used by the target environment.
!!! info "Recorded Credential Examples"
These examples use the `MOONGATE.LOCAL` domain and record Kerberos limitations from that setup. The separate [AWX Kerberos implementation](<../../../workflows/Automation/AWX/AWX Kerberos Implementation.md>) describes a `BUNNY-LAB.IO` configuration. Confirm which environment applies before using either example.
## 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.
```text 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. The separately documented AWX Kerberos implementation describes a different environment.
```text title="(Kerberos WinRM) nicole.rappe"
Credential Type: Kerberos WinRM
Username: nicole.rappe
Password: <Encrypted>
Kerberos Realm (Domain): MOONGATE.LOCAL
```
## Linux-based Credentials
```text title="(LINUX) nicole"
Credential Type: Machine
Username: nicole
Password: <Encrypted>
Privilege Escalation Method: sudo
Privilege Escalation Username: root
```
!!! note "Note"
`WinRM / Kerberos` based credentials do not currently work as-expected. That limitation belongs to this recorded example; consult the linked Kerberos workflow for the separate implementation.
## Related Documentation
- [Related AWX Documentation](<index.md>) — Find the connected deployments, procedures, and references for this subject.