Transitioning from an External KMS to PKCS #11 Secured Wallet
- Last Updated: May 20, 2026
- 1 minute read
- MarkLogic Server
- Version 12.0
- Documentation
Warning:
Moving from an external KMS to the internal KMS will downgrade your overall security, as the external KMS is more secure than the internal PKCS #11 secured wallet.
If for some reason you want to stop using your external KMS and revert to using the internal PKCS #11 secured wallet, use the steps in this section to transition to the internal PKCS #11 wallet.
To migrate encryption to internal the PKCS #11 wallet, do the following:
-
Important: Before you start the transition to an external KMS, back up the wallet that contains all of the internal keys.
-
Turn off encryption on all categories and force decryption of all encrypted forests by issuing a merge command.
-
Ensure that all data is un-encrypted, forest status reports encryption size.
-
Set the configuration back to the internal PKCS #11 KMS and rotate the key encryption keys. See Key Rotation for more information.
-
Re-index or force a merge of the database to re-encrypt your data.
Note:
Encrypted read-only forests will need to be set to
updates-allow all and mergeor they will be inaccessible.