Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-21868

User is getting Please check if xxxxxxx is valid Jira unique ID while authorization in MS Teams

      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

      Steps to Reproduce

      1. Type "connect" in MS Teams for Jira Server Bot
      2. Sign in with Microsoft account
      3. Click Authorize
      4. Enter Jira ID to connect to your Jira Server instance 
      5. Click "Connect" 

      Expected Results

      Authorization is successful 

      Actual Results

      The below exception is thrown in the xxxxxxx.log file:

      [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
      

      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.

          Form Name

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

              Unassigned Unassigned
              zvorona@atlassian.com Zoryana Vorona (Inactive)
              Affected customers:
              6 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated: