Pages not respecting internal_gitlab_server when fetching access token from GitLab
Hi, we are trying to setup GitLab Pages on a Omnibus installation on a VM that is within private network with no internet access. The GitLab and GitLab Pages are exposed to the internet via web proxy.
With that, we added the following configurations:
gitlab_pages['gitlab_server'] = "https://gitlab.example.com"
gitlab_pages['internal_gitlab_server'] = "https://gitlab.internal"
However, we noticed that while fetching access token from GitLab internally, it is still using gitlab_server
, resulting in dial tcp: lookup gitlab.example.com on <ns ip>:53: no such host
while querying internal DNS (we've copied /etc/resolv.conf
into pages_path).
Our question is that shouldn't Pages use the internal_gitlab_server in this case?
Proposal
The original purpose of internal_gitlab_server
is to support API-based configuration which is separate from authentication. However, we could use this flag in the auth package on lines 491 and 493