Frequently Asked Questions

To generate a registration token, you must first define an Application. For detailed instructions, refer to Managing Applications.

The registration token never expires. Refer to Managing Applications for details.

No, you can't reuse one registration token in different applications. Each application has its own registration token. All the clients that belong to the same application should use the same registration token.

You can only edit the latest version of a protection policy; however, you can view the older versions. Refer to Managing Protection Polices for details.

You can not protect a piece of data using old versions of protection policy. Protection is always performed using the latest protection policy version; however, if you want to reveal the data, you must use the corresponding old protection policy version. Refer to Managing Protection Polices for details.

If a protection policy is deleted, the protected data can not be revealed unless a protection policy with the same name, same version, and same attributes is created on the CipherTrust Manager. Refer to Managing Protection Polices for details.

Yes, you can reveal the output in different formats for different user sets. To achieve this, configure access policy and rules for different user sets. Application Data Protection allows you to reveal your data as Plaintext, Ciphertext, Error Replacement Value, and Masked value. Refer to Managing Access Polices for details.

Yes, you can delete erroneous client from the application. Refer to Clean Application for details.