doc/integration/_index.md
You can integrate GitLab with external applications for enhanced functionality.
Applications like Jenkins, Jira, and Slack are available as project integrations.
You can configure an external issue tracker and use:
You can integrate GitLab with authentication providers like LDAP and SAML.
For more information, see GitLab authentication and authorization.
Solutions like Akismet and reCAPTCHA are available for spam protection.
You can also integrate GitLab with the following security partners:
<!-- vale gitlab_base.Spelling = NO -->GitLab can check your application for security vulnerabilities. For more information, see Secure your application.
When working with integrations, you might encounter the following issues.
When you use a self-signed certificate to integrate GitLab with external applications, you might encounter SSL certificate errors in different parts of GitLab.
As a workaround, do one of the following:
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
Restart GitLab.
sudo gitlab-ctl restart
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.backtracejson.exception.classjson.exception.messagejson.messageTest Failed. Save AnywayWhen you configure an integration on an uninitialized repository, the integration might fail with
a Test Failed. Save Anyway error. This error occurs because the integration uses push data
to build the test payload when the project does not have push events.
To resolve this issue, initialize the repository by pushing a test file to the project and configure the integration again.