define | create security_policy

You can also specify one or more domains that the policy is associated with:

To specify that the policy is associated with one domain, specify the policy name and the domain as follows:

define | create security_policy policy_name <policy_name>/<domain name> policy_file <string>. 

For example:

create security_policy policy_name "OUR_POLICY/OUR_DOMAIN" policy_file "ourpolicy.txt"

If you enter the command in this way, the encrypt setting defaults to false: then if you specify one domain, you are prompted to enter and verify the password for that domain. If you specify multiple domains, you are prompted to enter and verify the password for each domain.

To create multiple domains associated with the policy, specify the policy name and a list of domains that the policy is associated with. Specify the domains separated by commas:

define | create security_policy policy_name "<string/string, string, string ...>" policy_file <string>

For example:

create security_policy policy_name "NEW_POLICY/MD1,MD2,MD3" policy_file "newpolicy.txt"

If you specify encryption, as-admin prompts you to specify and verify a new domain password and creates an encrypted private key in the Domain Identity section of the policy file.

If you specify encrypt false, the domain does not require a password, and as-admin creates an unencrypted private key in the policy file.

Policies can have more than one domain, where (in theory) each of them can have different validity days if the domain definitions are moved between policy files manually.