# Query on AD LDAP authentication

**URL:** <https://forum.ansible.com/t/query-on-ad-ldap-authentication/33295>\
**Category:** AWX Project\
**Tags:** awx, kubernetes\
**Created:** [July 1, 2020, 6:15pm UTC](https://forum.ansible.com/t/query-on-ad-ldap-authentication/33295 "2020-07-01T18:15:56Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vibin](https://avatars.discourse-cdn.com/v4/letter/v/2bfe46/32.png) [@Vibin](https://forum.ansible.com/u/Vibin)\
**Post date:** [July 1, 2020, 6:15pm UTC](https://forum.ansible.com/t/query-on-ad-ldap-authentication/33295/1 "2020-07-01T18:15:56Z")

</div>

Hello,

Got a query on AD LDAP authentication.

Let me explain my current setup Nd requirement.

We’ve deployed AWX version 12 on Kubernertes cluster. Got multiple instances of the application running on multiple worker nodes.

AD LDAP authentication is configured in AWX GUI.  
What happens now is whenever I login the authentication process happens on random nodes/instances. I was wondering whether there is any way to restrict the authentication process to specific nodes/instances.

Why am looking for this is because my K8s cluster consists of multiple nodes from different domains Nd we’ve different LDAP servers/ users under different domains. So if am logging in with user A on domain A Nd the authentication happens on instance B on domain B, it fails.

Looking forward for your response.

Regards,  
Vibin

---

<div class="post-metadata">

**Author:** ![Bill\_Nottingham1](https://avatars.discourse-cdn.com/v4/letter/b/58f4c7/32.png) [@Bill\_Nottingham1](https://forum.ansible.com/u/Bill_Nottingham1)\
**Post date:** [July 1, 2020, 7:04pm UTC](https://forum.ansible.com/t/query-on-ad-ldap-authentication/33295/2 "2020-07-01T19:04:13Z")

</div>

Vibin K Madampath (mm.vibin@gmail.com) said:

> AD LDAP authentication is configured in AWX GUI.  
> What happens now is whenever I login the authentication process happens on  
> random nodes/instances. I was wondering whether there is any way to  
> restrict the authentication process to specific nodes/instances.

No, the idea is that all application containers are running identically  
and are functionally interchangeable.

> Why am looking for this is because my K8s cluster consists of multiple  
> nodes from different domains Nd we've different LDAP servers/ users under  
> different domains. So if am logging in with user A on domain A Nd the  
> authentication happens on instance B on domain B, it fails.

I don't know the constraints that led to setting up K8S that way, but  
I'd strongly suggest not doing that. If you need to do that, restrict  
placement so containers only end up in one domain.

Bill

---

<div class="post-metadata">

**Author:** ![Vibin](https://avatars.discourse-cdn.com/v4/letter/v/2bfe46/32.png) [@Vibin](https://forum.ansible.com/u/Vibin)\
**Post date:** [July 1, 2020, 8:05pm UTC](https://forum.ansible.com/t/query-on-ad-ldap-authentication/33295/3 "2020-07-01T20:05:38Z")

</div>

Thanks for the response, Bill.

The rationale behind setting up K8s this way was to take advantage of the instance groups functionality Nd not having multiple AWX deployments.

Assigning instances on domain A to instance group A Nd domain B to instance group B. Instance group A and instance group B manages servers in domain A and domain B respectively.

Is there a better way to achieve this ??

Regards,  
Vibin

---

<div class="post-metadata">

**Author:** ![Vibin](https://avatars.discourse-cdn.com/v4/letter/v/2bfe46/32.png) [@Vibin](https://forum.ansible.com/u/Vibin)\
**Post date:** [July 7, 2020, 2:29pm UTC](https://forum.ansible.com/t/query-on-ad-ldap-authentication/33295/4 "2020-07-07T14:29:34Z")

</div>

Hello Bill,

Related to this, I have another question.

In our environment AWX is deployed in K8s Nd we’ve assigned instances to multiple instance groups based on the nodes they run on. But each time the pod/instance gets deleted, it comes back up with a different instance hostname.

Is there a way I can ensure the instances coming up on a specific node gets assigned to a specific instance group automatically? Like, instance coming up on node A gets assigned to instance group A.

Appreciate your response.

Regards,  
Vibin

---

<div class="post-metadata">

**Author:** ![Vibin](https://avatars.discourse-cdn.com/v4/letter/v/2bfe46/32.png) [@Vibin](https://forum.ansible.com/u/Vibin)\
**Post date:** [July 24, 2020, 6:32pm UTC](https://forum.ansible.com/t/query-on-ad-ldap-authentication/33295/5 "2020-07-24T18:32:48Z")

</div>

Hello Team,

Am not sure whether anyone had a similar requirement or not but if anyone has any idea how to achieve it or confirm whether it’s possible, it’ll be of great help.

As far as I know, there are three policies with Instance groups,

1. Minimum number of instances
2. Minimum percentage of all instances
3. Instance grouping by name

But the problem in my case is, every time the pod is restarted it gets a new hostname.

Appreciate earliest response.

Regards,  
Vibin

---

<div class="post-metadata">

**Author:** ![Vibin](https://avatars.discourse-cdn.com/v4/letter/v/2bfe46/32.png) [@Vibin](https://forum.ansible.com/u/Vibin)\
**Post date:** [August 3, 2020, 2:57pm UTC](https://forum.ansible.com/t/query-on-ad-ldap-authentication/33295/6 "2020-08-03T14:57:35Z")

</div>

Hello Team,

Appreciate if you could check and respond to my queries.

Regards,  
Vibin

---

<div class="post-metadata">

**Author:** ![Vibin](https://avatars.discourse-cdn.com/v4/letter/v/2bfe46/32.png) [@Vibin](https://forum.ansible.com/u/Vibin)\
**Post date:** [September 5, 2020, 6:41am UTC](https://forum.ansible.com/t/query-on-ad-ldap-authentication/33295/7 "2020-09-05T06:41:31Z")

</div>

Hello All,

For us, the solution was to use Container Groups instead of Instance Groups.

Regards,  
Vibin
