kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/doc/integration
History
Rémy Coutable fa82fd1283 Merge branch 'clarify-github-integration-docs' into 'master' 
Fix documentation for Github integration authorization callback url.

There are two callbacks that could be used with Github integration:

  * /import/github/callback (used by project import)
  * /users/auth/github/callback (used by OmniAuth)

Github's documentation suggests that authorization callback url should be
set to the longest common path.

https://developer.github.com/v3/oauth/#redirect-urls

Configuring according to the previous documentation resulted in a
redirect_uri_mismatch error from Github when logging in via OmniAuth.

See merge request !4111
2016-07-08 15:50:02 +00:00
..
img optimize png images losslessly using zopflipng 2016-06-29 19:22:15 +08:00
akismet.md Support Akismet spam checking for creation of issues via API 2016-02-02 11:25:44 -02:00
auth0.md Added omniauth-auth0 Gem + Applicable Documentation. 2016-03-16 13:12:20 +01:00
azure.md
bitbucket.md
cas.md Update cas.md to reflect the current syntax, and added that gitlab-ctl reconfigure should be run. 2016-04-21 10:30:27 +00:00
crowd.md
external-issue-tracker.md Added Bugzilla as external issue tracker option 2016-06-29 06:01:54 -04:00
facebook.md Move all integration docs images in a single directory 2016-01-24 21:22:19 +01:00
github.md Fix documentation for Github integration authorization callback url. 2016-05-10 19:15:26 -04:00
gitlab.md Move all integration docs images in a single directory 2016-01-24 21:22:19 +01:00
gmail_action_buttons_for_gitlab.md Move all integration docs images in a single directory 2016-01-24 21:22:19 +01:00
google.md Update Google integration API workflow 2016-05-23 18:35:04 +00:00
jira.md Move JIRA from integration to project_services 2016-01-25 10:08:11 +01:00
ldap.md Fix LDAP link and codeblock indentation 2016-04-05 17:04:16 +03:00
oauth_provider.md Refactor OAuth provider documentation 2016-02-03 13:18:37 +02:00
omniauth.md Fixed privilege escalation issue where manually set external users would be reverted back to internal users if they logged in via OAuth and that provider was not in the external_providers list. 2016-06-29 10:37:54 -05:00
README.md Change all occurrences of doc.gitlab.com to docs.gitlab.com 2016-05-13 16:26:56 -05:00
recaptcha.md
saml.md Implemented suggested fixes 2016-04-06 18:12:25 -05:00
shibboleth.md Fix wording around NGINX Shibboleth setup 2016-07-01 03:28:10 +00:00
slack.md update slack instructions 2016-03-01 19:17:22 +00:00
twitter.md Move all integration docs images in a single directory 2016-01-24 21:22:19 +01:00

README.md

GitLab Integration

GitLab integrates with multiple third-party services to allow external issue trackers and external authentication.

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

  • Jira Integrate with the JIRA issue tracker
  • External issue tracker Redmine, JIRA, etc.
  • LDAP Set up sign in via LDAP
  • OmniAuth Sign in via Twitter, GitHub, GitLab.com, Google, Bitbucket, Facebook, Shibboleth, SAML, Crowd and Azure
  • SAML Configure GitLab as a SAML 2.0 Service Provider
  • CAS Configure GitLab to sign in using CAS
  • Slack Integrate with the Slack chat service
  • OAuth2 provider OAuth2 application creation
  • Gmail actions buttons Adds GitLab actions to messages
  • reCAPTCHA Configure GitLab to use Google reCAPTCHA for new users
  • Akismet Configure Akismet to stop spam

GitLab Enterprise Edition contains advanced Jenkins support.

Project services

Integration with services such as Campfire, Flowdock, Gemnasium, HipChat, Pivotal Tracker, and Slack are available in the form of a Project Service.

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.
  2. If using Omnibus, you can add the certificate to GitLab's trusted certificates.

OS main trusted chain

This resource has all the information you need to add a certificate to the main trusted chain.

This answer at SuperUser also has relevant information.

Omnibus Trusted Chain

It is enough to concatenate the certificate to the main trusted certificate:

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

After that restart GitLab with:

sudo gitlab-ctl restart