Migrating site security for WebSphere Commerce
If you are migrating from WebSphere Commerce Version 7.0 to WebSphere Commerce Version 8.0, manually migrate your security configurations.
Procedure
-
If you enabled AES encryption on your WebSphere Commerce database and file system, migrate
your encryption settings files.
-
If you used the Key Locator Framework (KLF) in WebSphere Commerce 7.0, migrate your key
provider customizations. For more information about the KLF, see Key Locator Framework (KLF).
-
Open your version 7.0
WC_eardir/xml/config/wc-server.xml file, and look for the
KeysConfigFile
parameter. TheKeysConfigFile
parameter points to a separate custom key configuration XML. - Open your custom key XML file.
- The custom files that are referenced in this keys XML file must be copied to the same directories on your version 8.0 environment, and then deployed. For more information about this deployment process, see Deploying Java EE assets for a partial application.
-
Open your version 7.0
WC_eardir/xml/config/wc-server.xml file, and look for the
-
Review the values for
<AES_DB>
and<AES_Files>
in your version 7.0 WC_installdir\xml\product.xml file. Ensure your version 8.0 WC_installdir\xml\product.xml file contains the same values for each section, for example:<websphere> <commercesuite> ... <security> <AES_DB>true</AES_DB> <AES_Files>true</AES_Files> </security> </commercesuite> </websphere>
- If you updated your version 7.0 to meet the NIST SP 800-131A security standards, complete steps 9 - 12 on the following document:
- Migrate any other custom security files that were part of your version 7.0 security solution by copying the files to your version 8.0 environment and deploying the files.