Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G gitlab-pages
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 168
    • Issues 168
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 15
    • Merge requests 15
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • gitlab-pages
  • Issues
  • #548
Closed
Open
Issue created Feb 24, 2021 by Will Chandler@wchandlerDeveloper

Feature Request - Support mutual TLS when calling the GitLab API

When GitLab has been configured to require mTLS and Pages is on a separate host and using customer domains, calls to the GitLab internal API from Pages will be rejected.

For customers who require mTLS, it would be useful to add support mTLS for this call.

Similar work was done for Gitaly calls under gitlab#37090 (closed)

Update docs: https://docs.gitlab.com/ee/administration/pages/#running-gitlab-pages-on-a-separate-server

Edited Jan 02, 2022 by Ben Bodenmiller
Assignee
Assign to
Time tracking