The Application-level Gateway service definitions.
tab provides a single interface for managing all the different policies used inPolicies 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 (that is, previously defined) policies 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 MC 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.
tab of theNAT Policy: Policies for source and destination network address translation.
Authentication Policy: Policies describing how clients should be authenticated in different scenarios. See Chapter 15, Connection authentication and authorization for details.
Authentication Provider: AS authentication backends: databases providing user information for authentication. See Chapter 15, Connection authentication and authorization for details.
Authorization Policy: Policies describing how clients should be authorized in different scenarios. See Chapter 15, Connection authentication and authorization for details.
Detector Policy: Policies that start a service based on the protocol used in the connection.
Matcher Policy: Various matcher and filtering policies.
Resolver Policy: Simple domain name resolution policies.
Stacking Provider: External PNS hosts providing content filtering capabilities.
Published on June 04, 2020
© 2007-2019 BalaSys
Send your comments to support@balasys.hu