debian-mirror-gitlab/doc/integration/index.md

stage	group	info	comments
Manage	Integrations	To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments	false

GitLab integrations (FREE)

You can integrate GitLab with external services for enhanced functionality.

Services

Services such as Campfire, Flowdock, Jira, Pivotal Tracker, and Slack are available as integrations.

Issue trackers

You can use an external issue tracker with the GitLab issue tracker or use an external issue tracker only.

Authentication sources

You can integrate GitLab with the following authentication sources:

• Enable the Auth0 OmniAuth provider.
• Enable sign-in with Bitbucket accounts.
• Authenticate with Kerberos.
• Enable sign-in with LDAP.
• Enable creating OAuth 2.0 applications.
• Use OmniAuth to enable sign-in through:
  • Authentiq ID
  • Azure
  • Bitbucket
  • Crowd
  • Facebook
  • GitHub
  • GitLab.com
  • Google
  • SAML
  • Twitter
• Use GitLab as an OpenID Connect identity provider.
• Authenticate with Vault through GitLab OpenID Connect.
• Configure GitLab as a SAML 2.0 Service Provider.

Security enhancements

You can integrate GitLab with the following security enhancements:

• Akismet to reduce spam.
• Google reCAPTCHA to verify new users.

GitLab also provides features to improve the security of your own application. For more details, see Secure your application.

Security partners

You can integrate GitLab with several security partners. For more information, see Security partner integrations.

Continuous integration

You can integrate GitLab with the following external services for continuous integration:

• Jenkins CI.
• Datadog to monitor for CI/CD job failures and performance issues.

Feature enhancements

You can integrate GitLab with the following feature enhancements:

• Add GitLab actions to Gmail actions buttons.
• Configure PlantUML or Kroki to use diagrams in AsciiDoc and Markdown documents.
• Attach merge requests to Trello cards.
• Enable integrated code intelligence powered by Sourcegraph.
• Add Elasticsearch for Advanced Search.

Troubleshooting

SSL certificate errors

When integrating GitLab with services using a self-signed certificate, you might encounter SSL certificate errors in different parts of the application.

As a workaround, you can do one of the following:

• Add the certificate to the OS trusted chain. See:
  • Adding trusted root certificates to the server
  • How do you add a certificate authority (CA) to Ubuntu?
• In Omnibus GitLab, add the certificate to the Omnibus trusted chain:

  1. Install the self-signed certificate.

  2. Concatenate the self-signed certificate with the GitLab trusted certificate. The self-signed certificate might be overwritten during upgrades.

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

  3. Restart GitLab.

     sudo gitlab-ctl restart
     

Search Sidekiq logs in Kibana

To locate a specific integration in Kibana, use the following KQL search string:

`json.integration_class.keyword : "Integrations::Jira" and json.project_path : "path/to/project"`

You can find information in:

• json.exception.backtrace
• json.exception.class
• json.exception.message
• json.message