• Type: Bug
• Resolution: Unresolved
• Priority: Low (View bug fix roadmap)
• Fix Version/s: None
• Affects Version/s: JSMT 2022.08.101
• Component/s: Microsoft Teams for Jira Integration
• Labels:

  None

[JSWSERVER-21868] User is getting Please check if xxxxxxx is valid Jira unique ID while authorization in MS Teams

SET Analytics Bot made changes - 20/Dec/2024 4:32 AM

Support reference count

Original: 1

New: 2

SET Analytics Bot made changes - 16/May/2024 4:03 AM

Support reference count

New: 1

SET Analytics Bot made changes - 14/Oct/2023 2:55 AM

UIS

New: 1

Marek Parfianowicz made changes - 18/Sep/2023 12:17 PM

Status

Original: Gathering Impact [ 12072 ]

New: Long Term Backlog [ 12073 ]

Marek Parfianowicz made changes - 28/Aug/2023 12:59 PM

Status

Original: Needs Triage [ 10030 ]

New: Gathering Impact [ 12072 ]

Marek Parfianowicz made changes - 28/Aug/2023 12:59 PM

Description

Original: h3. Issue Summary When user tries to authorize it gives  the following message even though they use the ID Code from jira listed in the instruction. Please check if xxxxxxxxxxxxxxxxxx is valid Jira unique ID and Jira Server for Microsoft Teams app for your organization is installed h3. Steps to Reproduce  # Type "connect" in MS Teams for Jira Server Bot  # Sign in with Microsoft account  # Click Authorize  # Enter Jira ID to connect to your Jira Server instance   # Click "Connect"  h3. Expected Results Authorization is successful  h3. Actual Results The below exception is thrown in the xxxxxxx.log file: {noformat} [c.m.teams.service.SignalRService] startConnectionIfDisconnected() error (java.lang.RuntimeException): java.io.IOException: Unexpected response code for CONNECT: 403  Caesium-1-4 INFO ServiceRunner [c.m.teams.service.SignalRService] SignalR connection is currently false {noformat} h3. Workaround  Currently there is no known workaround for this behavior. A workaround will be added here when available. See this KB for some of the common problems https://confluence.atlassian.com/jirakb/connecting-microsoft-teams-to-jira-fails-1047553934.html

New: h3. Issue Summary When user tries to authorize it gives  the following message even though they use the ID Code from jira listed in the instruction. Please check if xxxxxxxxxxxxxxxxxx is valid Jira unique ID and Jira Server for Microsoft Teams app for your organization is installed h3. Steps to Reproduce  # Type "connect" in MS Teams for Jira Server Bot  # Sign in with Microsoft account  # Click Authorize  # Enter Jira ID to connect to your Jira Server instance   # Click "Connect"  h3. Expected Results Authorization is successful  h3. Actual Results The below exception is thrown in the xxxxxxx.log file: {noformat} [c.m.teams.service.SignalRService] startConnectionIfDisconnected() error (java.lang.RuntimeException): java.io.IOException: Unexpected response code for CONNECT: 403  Caesium-1-4 INFO ServiceRunner [c.m.teams.service.SignalRService] SignalR connection is currently false {noformat} h3. Workaround See this KB for some of the common problems https://confluence.atlassian.com/jirakb/connecting-microsoft-teams-to-jira-fails-1047553934.html There is also a possibility of having a PKIX error (Certification issue). If started to appear through the logs, the MSTEAMS will show as INACTIVE on the configuration page and the app will that wrong Unique Jira ID is used. The PKIX issue can be fixed by adding the certifications of SignalR and Azure in the Java TrustStore.

Marek Parfianowicz made changes - 28/Aug/2023 12:57 PM

Description

Original: h3. Issue Summary When user tries to authorize it gives  the following message even though they use the ID Code from jira listed in the instruction. Please check if xxxxxxxxxxxxxxxxxx is valid Jira unique ID and Jira Server for Microsoft Teams app for your organization is installed h3. Steps to Reproduce  # Type "connect" in MS Teams for Jira Server Bot  # Sign in with Microsoft account  # Click Authorize  # Enter Jira ID to connect to your Jira Server instance   # Click "Connect"  h3. Expected Results Authorization is successful  h3. Actual Results The below exception is thrown in the xxxxxxx.log file: {noformat} [c.m.teams.service.SignalRService] startConnectionIfDisconnected() error (java.lang.RuntimeException): java.io.IOException: Unexpected response code for CONNECT: 403  Caesium-1-4 INFO ServiceRunner [c.m.teams.service.SignalRService] SignalR connection is currently false {noformat} h3. Workaround  Currently there is no known workaround for this behavior. A workaround will be added here when available

New: h3. Issue Summary When user tries to authorize it gives  the following message even though they use the ID Code from jira listed in the instruction. Please check if xxxxxxxxxxxxxxxxxx is valid Jira unique ID and Jira Server for Microsoft Teams app for your organization is installed h3. Steps to Reproduce  # Type "connect" in MS Teams for Jira Server Bot  # Sign in with Microsoft account  # Click Authorize  # Enter Jira ID to connect to your Jira Server instance   # Click "Connect"  h3. Expected Results Authorization is successful  h3. Actual Results The below exception is thrown in the xxxxxxx.log file: {noformat} [c.m.teams.service.SignalRService] startConnectionIfDisconnected() error (java.lang.RuntimeException): java.io.IOException: Unexpected response code for CONNECT: 403  Caesium-1-4 INFO ServiceRunner [c.m.teams.service.SignalRService] SignalR connection is currently false {noformat} h3. Workaround  Currently there is no known workaround for this behavior. A workaround will be added here when available. See this KB for some of the common problems https://confluence.atlassian.com/jirakb/connecting-microsoft-teams-to-jira-fails-1047553934.html

Marek Parfianowicz made changes - 17/Aug/2023 9:31 AM

Affects Version/s	Original: 9.10.1 [ 105527 ]
Affects Version/s		New: JSMT 2022.08.101 [ 105741 ]

Marek Parfianowicz made changes - 17/Aug/2023 9:31 AM

Introduced in Version

Original: 9.1

Bugfix Automation Bot made changes - 10/Aug/2023 9:30 AM

Introduced in Version

New: 9.1

Load more older history items