Behavior during Import
- File formats supported include YAML and JSON.
- There are two registration methods: "New Creation" and "Overwrite".
- Deletion through import is not possible. Definitions not included in the import data will not be updated (they will remain unchanged).
- The unique key is "Priority of Encryption Policy".
Points to Note
- In the case of "Overwrite," information corresponding to the unique key mentioned above will be completely overwritten.
If there is an encryption policy that you want to keep as is, be sure to set a different priority.
Replace ␣ with half-width space | |
---|---|
Column | Description |
version:␣1 | Version (fixed) |
policies:
|
Create filters specified in the following lines. In JSON, use "Policies:". |
-␣priority: | Specify the priority |
␣␣from_address_group_name:␣ | Specify the sender's address group |
␣␣to_address_group_name:␣ | Specify the recipient's address group |
␣␣encryption_config_name:␣ | Specify the encryption type to apply to the combination of the previous recipient and sender Specify "Don't encrypt" if no encryption is desired. |
Example
・Combining "Sender_Fixed_Password(pw_yyyymmdd)" and "Recipient_Fixed_Password(pw_yyyymmdd)" sends with a fixed password and fixed ZIP file name.
・"Do Not Encrypt Recipients" is excluded from encryption
version: 1
policies:
- priority: 100
from_address_group_name: Sender_Fixed_Password(pw_yyyymmdd)
to_address_group_name: Recipient_Fixed_Password(pw_yyyymmdd)
encryption_config_name: Fixed Password(pw_yyyymmdd)
- priority: 1000
from_address_group_name: All
to_address_group_name: Do Not Encrypt Recipients
encryption_config_name: Don't encrypt