Run swift migration utility without storing atomic schema credentials as plain text in TF
(Doc ID 2763297.1)
Last updated on MARCH 31, 2021
Applies to:Oracle Financial Services Transaction Filtering - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
User scenario :
User unable to execute swift migration utility due to below reasons.
Due to security policy, user is not willing to store atomic schema credentials in in plain text in Dynamic.properties on Productive environments, as part of the SWIFT Migration Utility.
User want to know if there is a way to store credentials for a user without access to the atomic schema but able to run the utility (perhaps using db synonyms or a one-time script?)
Steps to reproduce :
Step 1 : Open winscp and goto below location for configuring swift migration utility
Location : $fic_home/Transaction_Processing/TF_Swift_Migration_Utlity/config
Step 2 : File Dynamic.properties
Step 3 : Check for password=$value$
Expected result :
Encrypted password must be used for Password parameter
Actual result :
Plain text is configured directly instead of encrypted password
Configure the swift migration utility for export/import swift messages
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document