# credential associations, lookup etc in awx.

**URL:** <https://forum.ansible.com/t/credential-associations-lookup-etc-in-awx/28011>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [July 10, 2018, 3:56pm UTC](https://forum.ansible.com/t/credential-associations-lookup-etc-in-awx/28011 "2018-07-10T15:56:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Raymond\_Ferguson](https://avatars.discourse-cdn.com/v4/letter/r/f08c70/32.png) [@Raymond\_Ferguson](https://forum.ansible.com/u/Raymond_Ferguson)\
**Post date:** [July 10, 2018, 3:56pm UTC](https://forum.ansible.com/t/credential-associations-lookup-etc-in-awx/28011/1 "2018-07-10T15:56:26Z")

</div>

It seems like there has been some discussion regarding how to associate per-host credentials, but I didn’t see anything come of it.

It looks possible with something like hashi vault based on templates, credential naming convention, and the hash\_vault lookup module, but I don’t see anything in AWX functionality to duplicate that functionality without writing my a lookup module, but I suspect the lookup would be pretty convoluted given that it executes on the \_task runner which would probably have to lookup the cred id, then submit a new job associate to the cred since it can’t request secrets by design.

Hashicorp example is from [https://www.ansible.com/blog/ansible-tower-feature-spotlight-custom-credentials](https://www.ansible.com/blog/ansible-tower-feature-spotlight-custom-credentials) and looks something like the following.

---

<div class="post-metadata">

**Author:** ![Christopher\_Meyers](https://avatars.discourse-cdn.com/v4/letter/c/3e96dc/32.png) [@Christopher\_Meyers](https://forum.ansible.com/u/Christopher_Meyers)\
**Post date:** [August 1, 2018, 9:33pm UTC](https://forum.ansible.com/t/credential-associations-lookup-etc-in-awx/28011/2 "2018-08-01T21:33:07Z")

</div>

Ansible lookup in a playbook is the way to go. AWX is only going to help you by protecting and injecting the hashicorp credentials.