2014-04-02 23:11:25 -04:00
# GitLab Integration
2016-01-08 04:40:45 -05:00
GitLab integrates with multiple third-party services to allow external issue
trackers and external authentication.
2014-04-24 18:48:22 -04:00
2014-04-02 23:11:25 -04:00
See the documentation below for details on how to configure these services.
2016-01-25 04:08:11 -05:00
- [Jira ](../project_services/jira.md ) Integrate with the JIRA issue tracker
2014-04-24 18:48:22 -04:00
- [External issue tracker ](external-issue-tracker.md ) Redmine, JIRA, etc.
- [LDAP ](ldap.md ) Set up sign in via LDAP
2016-01-22 11:57:29 -05:00
- [OmniAuth ](omniauth.md ) Sign in via Twitter, GitHub, GitLab.com, Google, Bitbucket, Facebook, Shibboleth, SAML, Crowd and Azure
2015-06-29 05:32:40 -04:00
- [SAML ](saml.md ) Configure GitLab as a SAML 2.0 Service Provider
2015-12-21 11:37:55 -05:00
- [CAS ](cas.md ) Configure GitLab to sign in using CAS
2014-04-24 18:48:22 -04:00
- [Slack ](slack.md ) Integrate with the Slack chat service
2015-03-03 10:38:38 -05:00
- [OAuth2 provider ](oauth_provider.md ) OAuth2 application creation
2015-09-17 11:08:10 -04:00
- [Gmail actions buttons ](gmail_action_buttons_for_gitlab.md ) Adds GitLab actions to messages
2015-12-27 23:36:33 -05:00
- [reCAPTCHA ](recaptcha.md ) Configure GitLab to use Google reCAPTCHA for new users
2016-01-09 14:30:34 -05:00
- [Akismet ](akismet.md ) Configure Akismet to stop spam
2014-05-17 04:41:12 -04:00
2016-01-08 04:40:45 -05:00
GitLab Enterprise Edition contains [advanced Jenkins support][jenkins].
2014-07-25 07:47:11 -04:00
## Project services
2016-01-08 04:40:45 -05:00
Integration with services such as Campfire, Flowdock, Gemnasium, HipChat,
Pivotal Tracker, and Slack are available in the form of a [Project Service][].
You can find these within GitLab in the Services page under Project Settings if
you are at least a master on the project.
Project Services are a bit like plugins in that they allow a lot of freedom in
adding functionality to GitLab. For example there is also a service that can
send an email every time someone pushes new commits.
Because GitLab is open source we can ship with the code and tests for all
plugins. This allows the community to keep the plugins up to date so that they
always work in newer GitLab versions.
For an overview of what projects services are available without logging in,
please see the [project_services directory][projects-code].
[jenkins]: http://doc.gitlab.com/ee/integration/jenkins.html
[Project Service]: ../project_services/project_services.md
[projects-code]: https://gitlab.com/gitlab-org/gitlab-ce/tree/master/app/models/project_services
2016-03-03 11:21:32 -05:00
## SSL certificate errors
When trying to integrate GitLab with services that are using self-signed certificates,
it is very likely that SSL certificate errors will occur on different parts of the
application, most likely Sidekiq. There are 2 approaches you can take to solve this:
1. Add the root certificate to the trusted chain of the OS.
1. If using Omnibus, you can add the certificate to GitLab's trusted certificates.
**OS main trusted chain**
This [resource ](http://kb.kerio.com/product/kerio-connect/server-configuration/ssl-certificates/adding-trusted-root-certificates-to-the-server-1605.html )
has all the information you need to add a certificate to the main trusted chain.
This [answer ](http://superuser.com/questions/437330/how-do-you-add-a-certificate-authority-ca-to-ubuntu )
at SuperUser also has relevant information.
**Omnibus Trusted Chain**
It is enough to concatenate the certificate to the main trusted certificate:
```bash
cat jira.pem >> /opt/gitlab/embedded/ssl/certs/cacert.pem
```
After that restart GitLab with:
```bash
sudo gitlab-ctl restart
```
