No ratings

Re-encrypting data may be necessary after database move


Re-encrypting data may be necessary after database move

This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.



When K2 databases are moved from one SQL server or instance to a different SQL server or instance, and the K2 Setup Manager is used to reconfigure the database connections in K2, encrypted data may no longer be accessible by K2.




K2 uses data encyption to protect sensitive data, such as SQLUM credentials, SmartObject service instance passwords, cached SSO and Run As credentials, and SmartBox data marked as encrypted. When the K2 database (consolidated or multiple) is relocated to a new SQL server, the K2 server may no longer be able to decrypt the data. The cause of this issue is due to the K2 Setup Manager dropping and recreating the encryption key based on the database move. This behavior no longer occurs in K2 4.6.3 and later releases.

If you reconfigured a database prior to K2 4.6.3, it may be necessary to re-encrypt the data manually. In most cases there is no encrypted data stored in the K2 database. However, if you believe you have encrypted data that is no longer accessible after a database move, contact K2 Support.


Labels: (1)
Version history
Last update:
‎05-20-2021 05:29 AM
Updated by: