The tab provides a single interface for managing all the different policies used in Zorp service definitions.
Policies are independent from service definitions. A single policy can be used in several services or proxy classes. Policies must be created and properly configured before they are actually used in a service. When configuring a service, only the existing policies, that is, the previously defined ones, can be selected.
On the left side of the Policies tab the existing policies are displayed in a tree, sorted by policy type. If a policy is selected, its parameters are displayed on the right side of the panel.
The policies available from the tab of the ZMC component are listed below. The subsequent sections describe the different policy types and their uses. The Authentication, Authentication Provider, and Authorization policies are discussed in Chapter 15, Connection authentication and authorization.
NAT Policy: NAT policies are created for source and destination network address translation.
Authentication Policy: These policies describe how clients should be authenticated in different scenarios. See Chapter 15, Connection authentication and authorization for details.
Authentication Provider: ZAS authentication backends: The databases provide user information for authentication. See Chapter 15, Connection authentication and authorization for details.
Authorization Policy: These policies describe how clients should be authorized in different scenarios. See Chapter 15, Connection authentication and authorization for details.
Detector Policy: These policies start a service based on the protocol used in the connection.
Matcher Policy: These are various matcher and filtering policies.
Resolver Policy: These policies are simple domain name resolution policies.
Stacking Provider: The stacking provider is an external Zorp host that provide content vectoring capabilities.
Published on May 30, 2024
© BalaSys IT Ltd.
Send your comments to support@balasys.hu
