Encryption

After the execution of migration scripts DB will be Sprint44 compatible with AES-256 encryption. 

Cloud Deployment (SaaS): In cloud deployment, there is only one component, which is the CI agent required for installation. For another component installation, contact Cross Identity Administrator or Support Team.

Follow the steps to convert Sprint35 DB to AES256 encryption:

1. Deploy the "EncUpdated.war" file shared in any Tomcat server where we have communication to above converted Sprint44 DB.
2. Once the EncUpdated.war file is extracted, stop the Tomcat and alter the DB details in "application.properties"  file of the path "EncUpdated/WEB-INF/classes".
3. Update the MySQL DB URL and above Sprint44 migrated DB name, DB username and DB password. Save and close the file.
4. Alter the log file path "log4j.appender.file.File=/tomcatpath/logs/encupdate.log" in "log4j.properties". Save and close the file.
5. Start the Tomcat server, and verify that it’s up and running.
6. Run the below curl command in the same Tomcat server where we deployed EncUpdated.war. Here, we need to ensure that Tomcat is running on port 8080. If any other, then, change in below curl command:

curl --location --request POST 'http://localhost:8080/EncUpdatelatest/updatealltables' \ --data-raw ''