Uploaded image for project: 'Opsgenie'
  1. Opsgenie
  2. OPSGENIE-1231

Microsoft Teams integration, when using @Opsgenie connect , approval screen comes blank with HTTP 400 errors on api

      Issue Summary

      Looks like authentication link from the "@Opsgenie connect" command in MS Teams is resulting in a blank screen

      Steps to Reproduce

      1. Login to teams.microsoft.com using Incognito or Private Mode
      2. Run the command:  @opsgenie connect
      3. clicking on the generated link to "authenticate in opsgenie" today, I get "Invalid authentication or session expired".
      4. Copying and pasting the authentication link into the URL of a logged in OG session, I get a blank screen where I captured the two har files from my test EU instance. 
      5. Customer had previously uploaded the following har files where they were getting a blank screen

      Expected Results

      Getting Opsgenie connection approval screen

      Support Case

      https://getsupport.atlassian.com/browse/OGSP-101341

       

      Actual Results

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

      ...
      

      Workaround


            [OPSGENIE-1231] Microsoft Teams integration, when using @Opsgenie connect , approval screen comes blank with HTTP 400 errors on api

            Generated token for the connect command was so long in Msteams integration. I have changed the token decoder to reduce the size of request parameter.

            It is fixed now. 

            Thanks
             

            Emel Kömürcü added a comment - Generated token for the connect command was so long in Msteams integration. I have changed the token decoder to reduce the size of request parameter. It is fixed now.  Thanks  

              ekomurcu@atlassian.com Emel Kömürcü
              11b3b30e0c37 Abhay Sarraf
              Affected customers:
              3 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: