How to Migrate Encryptable Fields To BRM Using CMT
(Doc ID 1528912.1)
Last updated on SEPTEMBER 08, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.
One of the scenario, for example, is the field PIN_FLD_PASSWD in class /service that should be migrated with CMT and be encrypted by BRM during migration. Tried changing the field to "Encryptable" in Developer Center and migrating one account using CMT with the data below for the service:
But after migrating it, the field password was stored as plain text.
The questions are:
1. Is there a way to make it automatic to BRM encrypt the data when migrating it using CMT if the field is defined as "Encryptable" in the data model?
2. If not, what is the correct way to migrate these encrypted fields into BRM?
3. Does one have to send the data already encrypted into the XML? What is the encryption algorithm that one must use so BRM can understand it?
The BRM release is 7.4 PS12.
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