Closed and locked metal padlock

Why does LaserPost request extended permissions?

Want to understand why you are getting these messages when doing a Fusion 360 post to LightBurn with LaserPost?

These dialogs appear because Fusion 360 requires elevated permission to be granted for some of the APIs (such as network access and file writing). The first warning alert is from LaserPost explaining what's about to happen, and the second is from Fusion 360 asking for permission.

LaserPost has a few features that depend on elevated permission being granted:

  • The Internet is used to determine if an update is available. This is a very simple API to the servers at nuCarve to retrieve version information on the current version. Here is an example call that might be made, which you can view directly in your browser:

  • Information about the version update is cached in a "laserpost.xml" file (stored in the configuration folder, which should be visible from the Assets/CAM Posts cloud project if using cloud storage for posts). This is used to remember the last time updates were checked as well as the last known available version information to reduce how often the Internet must be checked for updates.

The best solution is to simply check the "Remember my choice" option so you will not be bothered with these prompts in the future.

If you decline the permission, Fusion 360 will fail the post with an error (sadly, we can't detect and handle this gracefully). If you do not wish to allow these permissions yet want to use LaserPost, you must disable automatic updates which will instruct LastPost to no longer make any calls that require elevated permission. This is done by editing the machine in the Fusion 360 Machine Manager, selecting the "Post processing" tab, and adjusting the "Automatic update" property to "Never".

This article was last updated on December 5, 2022, and it's possible the code has changed since then. You can always open the source directly in Fusion 360, or check out the latest version on GitHub and check what it does with the restricted APIs. If you do find this article is incorrect or obsolete, consider posting a comment below or opening an issue on GitHub.

Share your thoughts.

    Join the discussion!

    We look forward to your thoughts, but please be patient as it may take a few hours to appear (thanks to spambots and unscrupulous hackers).

    Leave a Reply

    Your email address will not be published. Required fields are marked *