| Support |
| Site Admin |
|
| |
| Joined: 12 Mar 2004 |
| Posts: 370 |
| Location: Omaha, NE |
|
|
|
 |
|
 |
|
Creating test files when using Crypto Complete
Steps:
Create a test library.
Create a new Field Encryption Registry (validation list CRVL002). Example: CRTVLDL TESTLIB/CRVL002.
Create an empty physical file in the test library that will hold the encrypted field(s). This file should have the same field layout as the production physical file.
Use the ADDFLDENC command to add the test fields you want encrypted into the Registry. IMPORTANT:
Make sure the library for the physical file and the external files (if used) point to the test library.
Make sure the external file name matches exactly the name of the file used in production. Again, make sure to use the test library name.
Make sure the triggers are named exactly as that in production. If you used *GEN in production, then you can used *GEN here also
You can use the same key store you used in production, or make a copy of the key store in the test library
Activate the field(s) in the empty test physical using the ACTFLDENC command. This will set up the entry in the Field Encryption Registry (CRVL002) correctly.
Now delete the test physical file and all its logical files in the test library.
Delete any external files in the test library.
Restore the physical file with the encrypted values and the logical files into the test library.
Restore the external files into the test library
Test your applications to make certain the external files in test are getting updated and not the production files.
NOTE: If you ever change a Field Encryption Registry Entry to point to a new Key in production, you will need to also do this in the test environment. The key number on the registry entry must point to the same key in production as it does in test. |
|
