• Type: Bug
• Resolution: Duplicate
• Priority: Low
• Fix Version/s: None
• Affects Version/s: None
• Component/s: Knowledge Base
• Labels:

  None

1. 

   Find a Confluence page - Atlassian JIRA Extranet - Special Projects 2014-06-19 13-32-38 2014-06-19 13-33-19.jpg

   83 kB

   19/Jun/2014 3:34 AM

[JSDSERVER-604] Knowledge Base integration appears to be broken when confluence requires authentication

Owen made changes - 27/Mar/2019 5:46 AM

Workflow	Original: JSD Bug Workflow v5 - TEMP [ 2304425 ]	New: JAC Bug Workflow v3 [ 3125388 ]
Status	Original: Done [ 10044 ]	New: Closed [ 6 ]

Katherine Yabut made changes - 06/Jun/2017 3:16 AM

Workflow

Original: JSD Bug Workflow v5 [ 2058477 ]

New: JSD Bug Workflow v5 - TEMP [ 2304425 ]

Katherine Yabut made changes - 31/May/2017 12:38 AM

Workflow

Original: JSD Bug Workflow v5 - TEMP [ 2055718 ]

New: JSD Bug Workflow v5 [ 2058477 ]

Katherine Yabut made changes - 31/May/2017 12:35 AM

Workflow

Original: JSD Bug Workflow v5 [ 1956075 ]

New: JSD Bug Workflow v5 - TEMP [ 2055718 ]

Katherine Yabut made changes - 03/Apr/2017 5:18 AM

Workflow

Original: JSD Bug Workflow v4 [ 1615647 ]

New: JSD Bug Workflow v5 [ 1956075 ]

jonah (Inactive) made changes - 02/Apr/2017 11:41 AM

Description

Original: When trying to connect a ServiceDesk project to a Confluence space, and the Confluence instance does not allow anonymous access (presumably), the following error is always rendered: !https://s3.amazonaws.com/uploads.hipchat.com/10804/157981/FfTOlUDSuwMA3Ry/Selection_086.png! The AppLink is correctly configured on both ends, and other JIRA to Confluence integration which relies on the AppLink is also correctly working. For example: on a JIRA issue page, you can correctly link to a confluence page by searching for the page to link to, in the JIRA issue link dialog. !https://jira.atlassian.com/secure/attachment/121256/Find%20a%20Confluence%20page%20-%20Atlassian%20JIRA%20Extranet%20-%20Special%20Projects%202014-06-19%2013-32-38%202014-06-19%2013-33-19.jpg!

New: {panel:bgColor=#e7f4fa}   *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-604].   {panel} When trying to connect a ServiceDesk project to a Confluence space, and the Confluence instance does not allow anonymous access (presumably), the following error is always rendered: !https://s3.amazonaws.com/uploads.hipchat.com/10804/157981/FfTOlUDSuwMA3Ry/Selection_086.png! The AppLink is correctly configured on both ends, and other JIRA to Confluence integration which relies on the AppLink is also correctly working. For example: on a JIRA issue page, you can correctly link to a confluence page by searching for the page to link to, in the JIRA issue link dialog. !https://jira.atlassian.com/secure/attachment/121256/Find%20a%20Confluence%20page%20-%20Atlassian%20JIRA%20Extranet%20-%20Special%20Projects%202014-06-19%2013-32-38%202014-06-19%2013-33-19.jpg!

jonah (Inactive) made changes - 02/Apr/2017 11:41 AM

Link

New: This issue relates to JSDCLOUD-604 [ JSDCLOUD-604 ]

Katherine Yabut made changes - 19/Oct/2016 6:49 AM

Workflow

Original: JSD Bug Workflow v2 [ 1602783 ]

New: JSD Bug Workflow v4 [ 1615647 ]

Owen made changes - 22/Sep/2016 3:24 AM

Workflow

Original: JSD Bug Workflow [ 1398231 ]

New: JSD Bug Workflow v2 [ 1602783 ]

Marty (Inactive) made changes - 06/Sep/2016 2:43 AM

Component/s

New: Knowledge Base [ 26195 ]

Load more older events