Thanks for the pointer to setting of block_auto_created_users.

1. set it to true and restart gilab 8.12.6

[root@re02 ~]# grep block_auto_created_users /etc/gitlab/gitlab.rb
  block_auto_created_users: true
#     block_auto_created_users: false
# gitlab_rails['omniauth_block_auto_created_users'] = true
[root@ilclsre02 ~]# gitlab-ctl restart
ok: run: gitlab-workhorse: (pid 6661) 1s
ok: run: logrotate: (pid 6673) 0s
ok: run: nginx: (pid 6679) 0s
ok: run: postgresql: (pid 6688) 1s
ok: run: redis: (pid 6698) 0s
ok: run: sidekiq: (pid 6714) 1s
ok: run: unicorn: (pid 6719) 0s
[root@re02 ~]#

2. Delete userA  from admin console
3. Ask userA to login again
     3.1  step 2 and 3 are a few minutes apart. 
4. userA was able to login and gitlab account auto recreated again.
     4.1 from userA's profile page, userA is not locked.

So this setting is not working,

On Tuesday, October 11, 2016 at 3:36:53 PM UTC-5, T.J. Yang wrote:
> Hi
> I have ldap backend server configured and one can create gitlab account 
> automatically if the ldap account is valid.
> Is it possible the auto-create still going through administrator's 
> approval first then auto-create ?
> tj

You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To view this discussion on the web visit
For more options, visit

Reply via email to