Handling Netsuite Dynamic IP address issue in requesting a server with IP restriction in firewall

AI generated answer (using internal Slack threads):

****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** Handling NetSuite's dynamic IP address issue when requesting a server with IP restriction in the firewall can be challenging. NetSuite's IP addresses can change at any time without notice, and they do not provide a list of their IP addresses. Therefore, relying on IP addresses to directly access NetSuite services can result in unpredictable service outages or significant performance degradation. One possible solution is to set up an intermediary gateway service to receive requests from Suitelet to the third party. This way, the IP address of the gateway service, which you control, can be whitelisted instead of trying to whitelist NetSuite's dynamic IP addresses. Another approach is to use name-based rules instead of IP-based rules. However, this might not be possible if the third-party firewall only supports IP-based rules. In such a case, you could set up a cron job that parses the output of

dig

for NetSuite resources and updates/flushes rules accordingly. If the third party insists on IP-based rules, you might have to use the IP address blocks owned by NetSuite and possibly Oracle Cloud. However, this is not a recommended approach due to the reasons mentioned above. Lastly, using API keys or decent authentication instead of IP-based rules is a more reliable and secure approach. However, this would require the third party to support such authentication methods. Please note that these are general suggestions and the actual implementation might vary based on the specific requirements and constraints of your project.