PageRenderTime 24ms CodeModel.GetById 28ms RepoModel.GetById 0ms app.codeStats 0ms

/doc/integration/README.md

https://gitlab.com/Munken/gitlab-ce
Markdown | 65 lines | 44 code | 21 blank | 0 comment | 0 complexity | 47838d4aa9b93e3d503d5b5dffa106ce MD5 | raw file
    

  1. # GitLab Integration
    2. 

  2. 

  3. GitLab integrates with multiple third-party services to allow external issue
    4. 

  4. trackers and external authentication.
    5. 

  5. 

  6. See the documentation below for details on how to configure these services.
    7. 

  7. 

  8. - [JIRA](../project_services/jira.md) Integrate with the JIRA issue tracker
    9. 

  9. - [External issue tracker](external-issue-tracker.md) Redmine, JIRA, etc.
    10. 

  10. - [LDAP](ldap.md) Set up sign in via LDAP
    11. 

  11. - [OmniAuth](omniauth.md) Sign in via Twitter, GitHub, GitLab.com, Google, Bitbucket, Facebook, Shibboleth, SAML, Crowd and Azure
    12. 

  12. - [SAML](saml.md) Configure GitLab as a SAML 2.0 Service Provider
    13. 

  13. - [CAS](cas.md) Configure GitLab to sign in using CAS
    14. 

  14. - [OAuth2 provider](oauth_provider.md) OAuth2 application creation
    15. 

  15. - [Gmail actions buttons](gmail_action_buttons_for_gitlab.md) Adds GitLab actions to messages
    16. 

  16. - [reCAPTCHA](recaptcha.md) Configure GitLab to use Google reCAPTCHA for new users
    17. 

  17. - [Akismet](akismet.md) Configure Akismet to stop spam
    18. 

  18. - [Koding](../administration/integration/koding.md) Configure Koding to use IDE integration
    19. 

  19. 

  20. GitLab Enterprise Edition contains [advanced Jenkins support][jenkins].
    21. 

  21. 

  22. [jenkins]: http://docs.gitlab.com/ee/integration/jenkins.html
    23. 

  23. 

  24. 

  25. ## Project services
    26. 

  26. 

  27. Integration with services such as Campfire, Flowdock, Gemnasium, HipChat,
    28. 

  28. Pivotal Tracker, and Slack are available in the form of a [Project Service][].
    29. 

  29. 

  30. [Project Service]: ../project_services/project_services.md
    31. 

  31. 

  32. ## SSL certificate errors
    33. 

  33. 

  34. When trying to integrate GitLab with services that are using self-signed certificates,
    35. 

  35. it is very likely that SSL certificate errors will occur on different parts of the
    36. 

  36. application, most likely Sidekiq. There are 2 approaches you can take to solve this:
    37. 

  37. 

  38. 1. Add the root certificate to the trusted chain of the OS.
    39. 

  39. 1. If using Omnibus, you can add the certificate to GitLab's trusted certificates.
    40. 

    41. 

  41. **OS main trusted chain**
    42. 

  42. 

  43. This [resource](http://kb.kerio.com/product/kerio-connect/server-configuration/ssl-certificates/adding-trusted-root-certificates-to-the-server-1605.html)
    44. 

  44. has all the information you need to add a certificate to the main trusted chain.
    45. 

  45. 

  46. This [answer](http://superuser.com/questions/437330/how-do-you-add-a-certificate-authority-ca-to-ubuntu)
    47. 

  47. at Super User also has relevant information.
    48. 

  48. 

  49. **Omnibus Trusted Chain**
    50. 

  50. 

  51. [Install the self signed certificate or custom certificate authorities](http://docs.gitlab.com/omnibus/common_installation_problems/README.html#using-self-signed-certificate-or-custom-certificate-authorities)
    52. 

  52. in to GitLab Omnibus.
    53. 

  53. 

  54. It is enough to concatenate the certificate to the main trusted certificate
    55. 

  55. however it may be overwritten during upgrades:
    56. 

  56. 

  57. ```bash
    58. 

  58. cat jira.pem >> /opt/gitlab/embedded/ssl/certs/cacert.pem
    59. 

  59. ```
    60. 

  60. 

  61. After that restart GitLab with:
    62. 

  62. 

  63. ```bash
    64. 

  64. sudo gitlab-ctl restart
    65. 

  65. ```
    66. 

  66.