-
Bug
-
Resolution: Fixed
-
High
-
None
-
2
-
Severity 2 - Major
-
4
-
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
- Create/ install an app built with Forge that has a macro;
- 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
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
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.
Hey folks, just wanted to comment publicly that we're aware of a corner case with Confluence Automation that was not solved by our initial fix. We're working on it now.
Based on the last comment by Aditya Guntupalli I tested the Confluence automation using the rule, "Update label on a recurring basis", from the library and we are still getting the same error as before. I then tired creating several other rules with different triggers and actions and none of them work. They all fail with:
Error in execution:
Forbidden. Trace ID: [random trace id]
No related entities could be found.
Update: We have rolled out some changes so that any forge apps invoking `api.asUser()` requests should not be impacted by IP allowlists.
3ea8e896bf0d thank you for reaching out! At the moment we are in the process of testing and gradually rolling out a fix for this. We will post another update next week.
The last update I received, last September via a support issue I opened on this bug, was that the fix was scheduled to deliver late Q4 2022 with a deadline of 30 December 2022. As we are one month out from the deadline and there have been no informational updates to this issue from Atlassian, I would appreciate someone providing an update here addressing the question of when this fix can be expected.
I will be looking forward to this as well. It's a shame that I had to uninstall some add-ons and discontinue use of them because of this issue. A loss for me and the vendors who provide those add-ons.
Echoing the above, I am having difficulties with Automation for Confluence due to this issue. Any CQL in an action fails, and my automations cannot trigger via a webhook because the webhook call never makes it to the Confluence endpoint.
This is pretty limiting as far as what is possible in the A4C app with this bug in place.
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