Tutorials
These tutorials will explain how to use security.manager NEXT to restrict access to services. The tutorials are build on each other.
- Activate security.manager
-
In this tutorial, you will learn
-
how to set the sharing level in ArcGIS Portal and
-
how to enable security.manager NEXT for the SampleWorldCities service.
-
- Basic policy
-
In the following tutorials, you will learn how to create a basic policy that uses all kinds of restrictions. Thus, you will learn how the restrictions work together.
- Working with groups
-
In this tutorial, you will learn to define policies for two different ArcGIS Portal groups. ArcGIS Portal groups allow you to organize users and assign permissions for a selected group of users only.
- Fallback policy
-
In this tutorial, you will learn to provide a policy that provides a default level of access to all users who don’t match any specific policies. This policy provides access to the Cities (0) layer, limited to just the field CITY_NAME.
- Dynamic restrictions using user attributes
-
In the following tutorials, you will learn how to use security.manager NEXT to create restrictions that filter the access based on user attributes. To learn the basic about each kind of restriction follow the Basic policy section.
security.manager NEXT provides access to user information through special variables:
-
${user.username}: The authenticated user’s username -
${user.roles}: List of group IDs assigned to the user
These variables can be used in feature restriction queries to create dynamic, user-specific filters. They can also be used in spatial restrictions, as they also use queries.
-
- Automation & CI/CD
-
In the following tutorials, you will learn how to configure a GitHub repository for Continuous Integration/Continuous Deployment (CI/CD).