summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCindy Pallares 🦉 <cindy@gitlab.com>2018-01-31 15:49:41 +0000
committerCindy Pallares <cindy@gitlab.com>2018-02-12 18:38:35 -0500
commitd297de1d426cbb29b90e4b261a95f0262b3b6ddb (patch)
tree2cd018f8a1ec5ae79cffb82c58004a923c31a82b
parentee8e5a596c3d4e18a227185965b52baf6f66c5db (diff)
downloadgitlab-ce-docs/add-jira-sso-captcha-notes.tar.gz
Add SSO and CAPTCHA notes to JIRA docsdocs/add-jira-sso-captcha-notes
-rw-r--r--doc/user/project/integrations/jira.md16
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/user/project/integrations/jira.md b/doc/user/project/integrations/jira.md
index f77569e4886..c9456bf3a20 100644
--- a/doc/user/project/integrations/jira.md
+++ b/doc/user/project/integrations/jira.md
@@ -57,6 +57,12 @@ We have split this stage in steps so it is easier to follow.
---
+>**Notes:**
+- Our integration does not support SSO (such as SAML). You will need to create
+ an HTTP basic authentication password. You can do this by heading to the user
+ profile, looking up the username, and setting a password.
+
+
1. Now, let's create a `gitlab-developers` group which will have write access
to projects in JIRA. Go to the **Groups** tab and select **Create group**.
@@ -227,6 +233,16 @@ Make sure that the JIRA issue is not already marked as resolved, in other words
the JIRA issue resolution field is not set. (It should not be struck through in
JIRA lists.)
+
+### CAPTCHA
+
+CAPTCHA may be triggered after several consecutive failed log in attempts
+which may lead to a `401 unauthorized` error when testing your JIRA integration.
+If CAPTCHA has been triggered, you will not be able to use JIRA’s REST API to
+authenticate with the JIRA site. You will need to log in to your JIRA instance
+and complete the CAPTCHA.
+
+
[services-templates]: services_templates.md
[jira-repo-old-docs]: https://gitlab.com/gitlab-org/gitlab-ce/blob/8-13-stable/doc/project_services/jira.md
[jira]: https://www.atlassian.com/software/jira