Cannot unblock users after adding secondary AD server
Running this on a cloud server:
GitLab 8.12.13-ee
GitLab Shell 3.6.1
GitLab Workhorse 0.8.2
GitLab API v3
Git 2.7.4
Ruby 2.3.1p112
Rails 4.2.7.1
PostgreSQL
Installed from omnibus.
[root@dfwgitlab01 kmartin]# rpm -qi gitlab-ee-8.12.13-ee.0.el7.x86_64
Name : gitlab-ee
Version : 8.12.13
Release : ee.0.el7
Architecture: x86_64
Install Date: Thu 12 Jan 2017 07:58:09 PM CST
Group : default
Size : 888857124
License : MIT
Signature : (none)
Source RPM : gitlab-ee-8.12.13-ee.0.el7.src.rpm
Build Date : Wed 14 Dec 2016 07:20:15 PM CST
Build Host : runner-bac0abb1-project-283-concurrent-0
Relocations : /
Packager : GitLab Inc. <support@gitlab.com>
Vendor : Omnibus <omnibus@getchef.com>
URL : https://about.gitlab.com/
Summary : GitLab Enterprise Edition and GitLab CI (including NGINX, Postgres, Redis)
Description :
GitLab Enterprise Edition and GitLab CI (including NGINX, Postgres, Redis)
[root@dfwgitlab01 kmartin]#
I recently added a secondary LDAP authentication method because our existing AD environment is being decommed. It worked with some success. However most users are now locked. I don't know exactly what caused the lock but it's obviously related to recent work.
I'd like to unblock the users from the GUI but it's not possible. Steps to reproduce:
- Click on "Admin area" wrench icon with admin account
- Click on number of users
- Filter for blocked users
- Click on one user's name
- Observe status: Firstname Lastname (Blocked)
- Click blue "Unblock user" button
- Answer OK in dialog window
- Observe message at top of window: "This user cannot be unblocked manually from Gitlab"
I verified this user is not locked in AD. Also verified our domain service account used by Gitlab to perform LDAP queries is not locked.
I've looked up a few help articles from users in similar situations and was unable to run the various psql and rails commands on my server.