ARTIFACTORY: Managing Public Permissions for Edge Nodes

When do I need this?

In an Enterprise Plus setup, Access Federation can be used to synchronize permissions across different Artifactory clusters. It can also be used to push permissions to Edge nodes.

Let's say hypothetically you plan to set up Edge nodes to distribute packages to the public. The public shouldn't have access to the main production Artifactory instances, those need to stay internal.

You naturally need to manage permissions across the production Artifactory and can use Access Federation to do so.

To make matters more complicated, your company needs a separate set of public permissions for these public Edge nodes. Managing these two sets of permissions, one for the public and one for internal developers, can still be achieved with Access Federation. 

Since Access Federation's system doesn't have the ability to filter sets of Users, Groups, or Permissions, you will need to set up 2 separate permission sets by using 2 Mission Control systems. One set will be for internal developers, and the other will be for public distribution:


 

Deep Dive

Generally speaking, all the Users you create on your internal, production Artifactory instances will have permissions to deploy new files and delete internal "dev" packages. Meanwhile, the public Edge users will only need read access to these files.

One way to achieve this setup is to have two mission controls. One Mission Control would be for the internal production Artifactory cluster network, and the second Mission Control would attached to an edge node. You could use the Edge Mission Control to manage Access Federation for the other edge nodes in the system. This will not interfere with the permissions on your main production Artifactory instance.

Access Federation would synchronize all the different "read" access public users would need. This way IoT devices and other public accounts would only have access to certain edge node artifacts.