# Discourse Assign - bug taking site down

**URL:** <https://meta.discourse.org/t/discourse-assign-bug-taking-site-down/128049>\
**Category:** Bug\
**Created:** [September 9, 2019, 3:05pm UTC](https://meta.discourse.org/t/discourse-assign-bug-taking-site-down/128049 "2019-09-09T15:05:20Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![diwr](https://avatars.discourse-cdn.com/v4/letter/d/41988e/32.png) [@diwr](https://meta.discourse.org/u/diwr)\
**Post date:** [September 25, 2019, 7:13am UTC](https://meta.discourse.org/t/discourse-assign-bug-taking-site-down/128049/13 "2019-09-25T07:13:09Z")

</div>

Hello Roman,  
we’ve got a simmilar problem with the discourse-assign plugin on our site after upgrading to 2.4.0beta4.

The Problem only appears on users logging in via ldap. (we use “[GitHub - jonmbake/discourse-ldap-auth: Discourse plugin to enable LDAP/Active Directory authentication. · GitHub](https://github.com/jonmbake/discourse-ldap-auth)” for the ldap connection)

the response to the DB.query is:  
=\> [“staff”]  
but " Group.where(name: ‘staff’).pluck(:id).join(‘|’)" returns “”.

Btw: On Version “2.4.0.beta1 +203” the responses are similar, but login by ldap is possible. (ldap version 0.4.0, assign version 0.1)

Any help welcome,  
Thanks,  
Frank

---

_[View the full topic](https://meta.discourse.org/t/discourse-assign-bug-taking-site-down/128049)._
