Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #4794

Closed
Open
Created Aug 16, 2013 by Administrator@rootOwner

No-certificate default behaviour

Created by: mbajur

Hello there! I have a quick question regarding no-certificate behaviour of GitLab.

When doing pull from server, if user has no certificate set or his certificate is wrong, GitLab (git in terminal) asks user for git user password. For instance, if you're trying to make a pull from GitHub and you have no certificate set, git pull throws access denied (or something like that, i can't remember the exact message right now) error.

Is there any way to make it also in my GItLab instance? It can be a bit confusing. Thanks in advance.

Assignee
Assign to
Time tracking