Security Policy Files
A security policy file contains the security settings for one or more security domains. Security domain requestors use a security token file that you generate from a security policy file to connect to a metaspace contained in the Metaspace Access List for a security domain that is defined in the security policy file.
Applications that connect to a metaspace listed in the Metaspace Access List for a security domain in a security policy file use the security policy file to become security domain controllers for the metaspace.
Applications that connect to a metaspace listed in the Metaspace Access List for a security domain in a security policy file, but do not use the security policy file to connect to the metaspace, become security domain requestors for the metaspace.
Procedure
- Creating a Security Policy File
You generate security policy files using the Admin CLI. You then edit the settings for each security domain within the security policy file to fit your particular security needs. - Security Domain Settings
- Validating a Security Policy File
You validate security policy files using the Admin CLI. After you have finished editing the security settings for the security domains included in the security policy file, validate the file to make sure that your edits to the file seem reasonable before you try to actually use the file - Security Policy File Keys and Certificates
For each security domain, the security policy file also contains: