当用户未能通过LDAP登录时，GitLab是否阻止了他

我们在Linux服务器上安装了GitLab Community Edition 9.1.3（2e4e522）。我们使用广告登录是因为我们的公司政策

配置文件

/etc/gitlab/gitlab.rb

 gitlab_rails['ldap_enabled'] = true
 gitlab_rails['ldap_servers'] = YAML.load <<-'EOS' # remember to close this block with 'EOS' below
   main: # 'main' is the GitLab 'provider ID' of this LDAP server
     label: 'LDAP'
     host: '{HOST}'
     port: 389
     uid: 'sAMAccountName'
     method: 'plain'
     bind_dn: 'CN=SVCJAVACZ,OU=FUNCTIONAL,OU=Users,OU=CZ,OU=MCC,DC=r3,DC=madm,DC=net'
     password: '{PASSWORD}'
     active_directory: true
     allow_username_or_email_login: false
     block_auto_created_users: false
     base: 'DC=r3,DC=madm,DC=net'
     user_filter: ''
     attributes:
       username: ['uid', 'userid', 'sAMAccountName']
       email:    ['mail', 'email', 'userPrincipalName']
       name:       'cn'
       first_name: 'givenName'
       last_name:  'sn'
 EOS

从文件

unicorn\u stdout.log

：

I, [2017-05-28T15:51:55.388593 #14907]  INFO -- omniauth: (ldapmain) Callback phase initiated.
E, [2017-05-28T15:51:55.569159 #14907] ERROR -- omniauth: (ldapmain) Authentication failure! invalid_credentials encountered.

从

sudogitlab rake gitlab:env:info

中提到的命令：

System information
System:         Ubuntu 16.04
Current User:   git
Using RVM:      no
Ruby Version:   2.3.3p222
Gem Version:    2.6.6
Bundler Version:1.13.7
Rake Version:   10.5.0
Redis Version:  3.2.5
Git Version:    2.11.1
Sidekiq Version:4.2.7

GitLab information
Version:        9.1.3
Revision:       2e4e522
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     postgresql
URL:            http://{URL}
HTTP Clone URL: http://{URL}/some-group/some-project.git
SSH Clone URL:  git@{URL}:some-group/some-project.git
Using LDAP:     yes
Using Omniauth: no

GitLab Shell
Version:        5.0.2
Repository storage paths:
- default:      /var/opt/gitlab/git-data/repositories
Hooks:          /opt/gitlab/embedded/service/gitlab-shell/hooks
Git:            /opt/gitlab/embedded/bin/git

GitLab中是否有任何缓存会定期为尝试登录但失败的用户发送阻塞命令（因此从此被阻塞）

---

或者现在有什么建议可以考虑吗？有什么想法吗？

正如文档中所述，在文件

application.log

中也应该有一个日志。再加上这个，就可以得到整个picture@secustor那天的

应用程序.log

都是空的。。但我会在这里说明；）

System information
System:         Ubuntu 16.04
Current User:   git
Using RVM:      no
Ruby Version:   2.3.3p222
Gem Version:    2.6.6
Bundler Version:1.13.7
Rake Version:   10.5.0
Redis Version:  3.2.5
Git Version:    2.11.1
Sidekiq Version:4.2.7

GitLab information
Version:        9.1.3
Revision:       2e4e522
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     postgresql
URL:            http://{URL}
HTTP Clone URL: http://{URL}/some-group/some-project.git
SSH Clone URL:  git@{URL}:some-group/some-project.git
Using LDAP:     yes
Using Omniauth: no

GitLab Shell
Version:        5.0.2
Repository storage paths:
- default:      /var/opt/gitlab/git-data/repositories
Hooks:          /opt/gitlab/embedded/service/gitlab-shell/hooks
Git:            /opt/gitlab/embedded/bin/git