Defining application policy
Use Access Gateway to configure one or more access policies per application. Policies are applied to URL resources within an application and you can set them to allow or deny:
- Access to an application by any authenticated user (default).
- No authentication access (to anyone) for an application.
- Specific users to access an application.
- Specific groups to access an application.
- Access to an application based on any IdP user profile attribute.
- Granular access based on application URLs or deep links.
- Custom access based on advanced configuration.
During this task you will creating, configuring, and managing Access Gateway application policies.
When configuring application access policy its important to understand that all application access policy is derived from, or inherits from, the original group specified in the applications Essentials section. Before any access policy is applied to any application URI, a check is made against the applications group setting, which may grant or deny access to the application as a whole.
Configuring application access policy
To configure an application policy:
- Navigate to the Access Gateway Admin UI console.
Click the Applications tab.
Select an application that requires new policy and click Edit.
Select the Policies sub-tab.
- Choose one of:
Add a new policy Delete an existing policy Modify an existing policy
The default root (/) policy cannot be deleted or modified.
- Click Add () in the policy list header and choose one of:
- Not Protected
- Protected Rule
- Custom - To add a custom policy you must select another policy type and then change its type to Custom.
See About Access Gateway policy types for type details.
- In the Resource Path, enter the URI to the resource being protected.
Custom policy allows administrators to add a regular expression as Resource Path.
URI's matching this regular expression will have this policy applied.
Policy URI must also be unique across Login, Logout, and Error behaviors. Access Gateway does not support using the same URL for multiple behaviors or policies.
- If required, clear the Case Sensitive checkbox to mark the URI case insensitive. See About application policy Resource Path precedencefor more information on Resource Path, policy precedence, general matching, and case sensitive or insensitive matching.
Introduced in Access Gateway version 2021.2.1
Only Custom policy allows the use of regular expressions in Resource Path.
- For Protected, Protected Rule, and Adaptive Rule: In Resource Matching Rule enter a regex expression representing the users who should be granted access to the resource. See Example Access Gateway policy for examples of expressions.
- Click Okay to add the policy or Cancel to cancel.
Note that policies are applied and executed according to URI precedence. See About application policy Resource Path precedence for more information.
- Click Delete () next to the policy to be deleted.
- In the confirm dialog box, click Yes to delete the attribute or No to cancel the delete operation.