Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-1427

Forge apps might not work as expected if IP allowlist is enabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • IP Allowlisting
    • None

      Issue Summary

      When using apps (add-ons) developed with Forge, their macros may not work as expected if the user has IP Allowlisting enabled. Sometimes the macro will throw an error or simply will not work at all.

      Steps to Reproduce

      1. Create/ install an app built with Forge that has a macro;
      2. Try to use the macro provided by the app;

      We noticed the problem happens when the macro / app tries to perform any type of API request, which seems to be blocked by the IP Allowlist.

      Expected Results

      The macro should work without problems.

      Actual Results

      Depending on the macro, it might throw an error os simply not work at all.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [ACCESS-1427] Forge apps might not work as expected if IP allowlist is enabled

            Felipe Oliveira made changes -
            Remote Link Original: This issue links to "ACE-624 (Jira)" [ 655076 ] New: This issue links to "ACE-624 (Hello Jira)" [ 655076 ]
            Rodrigo B. made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 746691 ]
            Rebekkah Dorhout made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 728930 ]
            Rebekkah Dorhout made changes -
            Remote Link Original: This issue links to "Page (Confluence)" [ 651491 ]
            Aditya Guntupalli made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]

            Aditya Guntupalli added a comment -

            Hi everyone,

            This is Aditya from the IPAllowlisting team. Thank you for your patience as we work on fixing this bug. We pushed a fix to solve this issue for Automation For Confluence. You should no longer be seeing these errors when using Automation For Confluence. We have created https://jira.atlassian.com/browse/ACCESS-1442 to separately track IPAllowlisting errors for `asApp` requests and we will be closing this issue. Please follow https://jira.atlassian.com/browse/ACCESS-1442 if you are impacted by IPAllowlisting errors on `asApp` requests.

            Best,

            Aditya

            Aditya Guntupalli added a comment - Hi everyone, This is Aditya from the IPAllowlisting team. Thank you for your patience as we work on fixing this bug. We pushed a fix to solve this issue for Automation For Confluence. You should no longer be seeing these errors when using Automation For Confluence. We have created https://jira.atlassian.com/browse/ACCESS-1442 to separately track IPAllowlisting errors for `asApp` requests and we will be closing this issue. Please follow https://jira.atlassian.com/browse/ACCESS-1442 if you are impacted by IPAllowlisting errors on `asApp` requests. Best, Aditya

            Rick Olson added a comment -

            Hello!

            We are using IP Allowlisting and trying to use the new Behaviours capability from Adaptavist. 

            Is there ETA on when the in-progress bug might be fixed?

            Thans!

            -Rick

            Rick Olson added a comment - Hello! We are using IP Allowlisting and trying to use the new Behaviours capability from Adaptavist.  Is there ETA on when the in-progress bug might be fixed? Thans! -Rick
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2

            Atlassian-SCSK開発者 added a comment - - edited

            Changing `asApp()` to `asUser()` worked for invoking requests. Is there any workaround for the requests that are restricted to `asApp()` api calls such as the product events and the scheduled triggers? 
            We tried updating @forge/bridge but didn't work.

            Atlassian-SCSK開発者 added a comment - - edited Changing `asApp()` to `asUser()` worked for invoking requests. Is there any workaround for the requests that are restricted to `asApp()` api calls such as the product events and the scheduled triggers?  We tried updating @forge/bridge but didn't work.
            SET Analytics Bot made changes -
            Support reference count Original: 9 New: 1

              ecf27a037d15 Aditya Guntupalli
              gtworkowski Guilherme T (Inactive)
              Affected customers:
              18 This affects my team
              Watchers:
              42 Start watching this issue

                Created:
                Updated:
                Resolved: