Column Handling in Java

To minimize the impact of the encryption on the Java logic a method was found to load the decrypted column into the normal column slot in the business class before processing. This then can carry on with all normal processing as before. The Java is not responsible for encrypting the column back to the database as all the noted tables now have workflow on them and the logic was put into these triggers to handle it since workflow needs the values in the clear to process. Oracle Reports

Oracle Reports will not be changed to show encrypted column values. They cannot be supported on any table that has the encryption turned on. Triggers

ECT, EID, PPRD, and RCA all had Workflow triggers on them and workflow needs the values in the clear to work with. Due to this we recognized that the best place for doing the encryption of a value on an insert or update was within these triggers. Because of this we added workflow to the PDP (Deposits) table as well. To be consistent we then also added special triggers to the MUS and MRO tables to handle the encrypting of the passwords there whether still using the old P2k method or the new real method.

• Do Oracle Reports support column encryption? o If you use an Oracle Report that attempts to utilize an encrypted column the report will fail.

• Will users that run Discoverer or other external reports be affected? o As long as the report is using the High Line provided system views the reports will not be affected otherwise the external report fields will need to be updated to use the non-encrypted field.