PageRenderTime 25ms CodeModel.GetById 11ms RepoModel.GetById 0ms app.codeStats 0ms

/doc/integration/README.md

https://gitlab.com/cuongtm/gitlab-ee
Markdown | 63 lines | 43 code | 20 blank | 0 comment | 0 complexity | baa6736fe1f0f80af280c54c976fa20d MD5 | raw file
  1. # GitLab Integration
  2. GitLab integrates with multiple third-party services to allow external issue
  3. trackers and external authentication.
  4. See the documentation below for details on how to configure these services.
  5. - [Jira](../project_services/jira.md) Integrate with the JIRA issue tracker
  6. - [External issue tracker](external-issue-tracker.md) Redmine, JIRA, etc.
  7. - [LDAP](ldap.md) Set up sign in via LDAP
  8. - [Jenkins](jenkins.md) Integrate with the Jenkins CI
  9. - [OmniAuth](omniauth.md) Sign in via Twitter, GitHub, GitLab.com, Google, Bitbucket, Facebook, Shibboleth, SAML, Crowd and Azure
  10. - [SAML](saml.md) Configure GitLab as a SAML 2.0 Service Provider
  11. - [CAS](cas.md) Configure GitLab to sign in using CAS
  12. - [Slack](slack.md) Integrate with the Slack chat service
  13. - [Kerberos](kerberos.md) Integrate with Kerberos
  14. - [OAuth2 provider](oauth_provider.md) OAuth2 application creation
  15. - [Gmail actions buttons](gmail_action_buttons_for_gitlab.md) Adds GitLab actions to messages
  16. - [reCAPTCHA](recaptcha.md) Configure GitLab to use Google reCAPTCHA for new users
  17. - [Akismet](akismet.md) Configure Akismet to stop spam
  18. GitLab Enterprise Edition contains [advanced Jenkins support][jenkins].
  19. [jenkins]: http://doc.gitlab.com/ee/integration/jenkins.html
  20. ## Project services
  21. Integration with services such as Campfire, Flowdock, Gemnasium, HipChat,
  22. Pivotal Tracker, and Slack are available in the form of a [Project Service][].
  23. [Project Service]: ../project_services/project_services.md
  24. ## SSL certificate errors
  25. When trying to integrate GitLab with services that are using self-signed certificates,
  26. it is very likely that SSL certificate errors will occur on different parts of the
  27. application, most likely Sidekiq. There are 2 approaches you can take to solve this:
  28. 1. Add the root certificate to the trusted chain of the OS.
  29. 1. If using Omnibus, you can add the certificate to GitLab's trusted certificates.
  30. **OS main trusted chain**
  31. This [resource](http://kb.kerio.com/product/kerio-connect/server-configuration/ssl-certificates/adding-trusted-root-certificates-to-the-server-1605.html)
  32. has all the information you need to add a certificate to the main trusted chain.
  33. This [answer](http://superuser.com/questions/437330/how-do-you-add-a-certificate-authority-ca-to-ubuntu)
  34. at SuperUser also has relevant information.
  35. **Omnibus Trusted Chain**
  36. It is enough to concatenate the certificate to the main trusted certificate:
  37. ```bash
  38. cat jira.pem >> /opt/gitlab/embedded/ssl/certs/cacert.pem
  39. ```
  40. After that restart GitLab with:
  41. ```bash
  42. sudo gitlab-ctl restart
  43. ```