Exporting a Policy

The Policy Manager allows you to export a policy to a file. Use this feature to share policies internally or externally, or to save copies of policies for record-keeping purposes. Exported policies that are saved locally can be renamed, deleted, or edited by replacement.
gateway83
The Policy Manager allows you to export a policy to a file. Use this feature to share policies internally or externally, or to save copies of policies for record-keeping purposes. Exported policies that are saved locally can be renamed, deleted, or edited by replacement.
It is recommended that you only export valid policies. Validation confirms the proper configuration and organization of a policy. See Validating a Policy for more information. An exported policy may contain disabled assertions. If security zones have been defined, you must have Read permissions to the policy in order to export.
The portable policy XML file generated during export includes references to:
  • The identity providers belonging to the users and groups in the policy
  • The JMS routing endpoints, or destinations, if included in the policy, and
  • Any custom assertions, if present in the policy.
When exporting a policy using the browser client version of the Policy Manager, the Java applet must be running in the trusted mode. For more information, see Policy Manager Browser Client.
To export a policy:
  1. Open the policy to be exported using either of the following methods:
    • Right-click the service name in the Services and Policies list and then select 
      Active Policy Assertions
      . Or,
    • Double-click the service name in the Services and Policies list.
  2. Click [
    Export Policy
    ] on the Policy Tool Bar or select The Export Policy dialog appears.
  3. Do one of the following:
    • If using the standard client:
      Either use the default directory offered or navigate to another location. If you use the default location (".l7tech\policy.templates"), the exported policy will appear under the Policy Templates section of the [Assertions] tab.
      Only exported policies saved as a template in the default directory will appear under the Policy Templates section of the [Assertions] tab. Policies saved to any other location will not appear in the Policy Templates section. Policies can be imported regardless of their saved locations. 
    • If using the browser client:
      Navigate to a folder of your choice to save the template.
      Be sure to note the location of the saved templates for later import. This is because there is no Policy Templates section in the [Assertions] tab for the browser client version.
  4. Enter a descriptive name for the exported policy and then click [
    Save
    ]. The policy is exported as a portable XML file which encapsulates all of the assertions and back-end settings. The policy appears under Policy Templates in the [Assertions] tab (standard client version only).
You can open the exported XML file in a text editor to view policy details. Be sure you have a backup before you make any modifications to the file.