Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #28788

Closed (moved)
(moved)
Open
Created Dec 08, 2018 by juga @juga

Document configuration verify option and disable urllib3

In #28647 (moved) we say that it's ok that the destination certificate is self-signed. There was no any documentation about how sbws could accept self-signed certificates and the default was hard-coded. There're different ways to validate certificates with Python requests (http://docs.python-requests.org/en/master/user/advanced/#ssl-cert-verification), but the only one implemented is to don't verify the certificate. The simpler way to accept self-signed certificates is to don't verify it. When using this option, there're urllib3 warnings that should be disabled.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking