Missing members from group via API

Summary

I'm trying to retrieve the users from a group in Gitlab by the API. This call is done: https://gitserver/api/v3/groups/170/members. This should list all members of group with ID 170. But currently it only show the list in Page 1 of Gitlab, under Groups.

Steps to reproduce

Do a login with a user with credentials to see the users in a group
Go to https://gitserver/api/v3/groups/170/members
The result gave back a very short list of these members. There are members missing

Expected behavior

I expected to see the full list of all members of the given group

Actual behavior

I did see a short list of the members, probably only the first page which is shown in the UI.

Relevant logs and/or screenshots

None

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com) Tested with an on-premise server running GitLab Community Edition 8.14.3.

Results of GitLab application Check

Checking GitLab Shell ...

GitLab Shell version >= 4.0.0 ? ... OK (4.0.0)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
170/2 ... ok
**...long list all yes...**
170/305 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
Send ping to redis server: OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking Reply by email ...

Reply by email is disabled in config/gitlab.yml

Checking Reply by email ... Finished

Checking LDAP ...

Server: ldapmain
LDAP authentication... Success
LDAP users with access to your GitLab server (only showing the first 100 results)
        ....
        DN: CN=Demo,OU=test accounts,OU=Users,OU=NNNNNN,DC=nnnnnn,DC=local   sAMAccountName: demo1
        ....
Checking LDAP ... Finished

Checking GitLab ...

Git configured with autocrlf=input? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory setup correctly? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
projects have namespace: ...
170/2 ... yes
**...long list all yes...**
170/305 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.3.1)
Your git bin path is "/opt/gitlab/embedded/bin/git"
Git version >= 2.7.3 ? ... yes (2.7.4)
Active users: 173

Checking GitLab ... Finished

Results of GitLab environment info

System information
System:
Current User:   git
Using RVM:      no
Ruby Version:   2.3.1p112
Gem Version:    2.6.6
Bundler Version:1.13.6
Rake Version:   10.5.0
Sidekiq Version:4.2.1

GitLab information
Version:        8.14.3
Revision:       2f0065b
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     postgresql
URL:            https://**<gitserver>**
HTTP Clone URL: https://**<gitserver>**/some-group/some-project.git
SSH Clone URL:  git@**<gitserver>**:some-group/some-project.git
Using LDAP:     yes
Using Omniauth: no

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

Possible fixes

Don't rely on the API and use the GUI, not a really workaround for scripts.