Clarification About The Decrypt Entry in Dm_oracle Pin.conf
(Doc ID 2505875.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Upgraded the test environment to 7.5PS22, changed the default crypt scheme setting in dm_oracle from MD5 to AES, and the "testnap" was not working without adding a decrypt entry in ~/sys/dm_oracle/pin.conf for MD5 with an appropriate key;
It was observed (in 7.4MPS2) that, to successfully connect to CM with the "testnap", the decrypt entry could be removed only after executing pin_crypt_upgrade to convert the pcm_client and admin_client passwords (among other objects whose fields may have been previously encrypted with MD5).
Why is the difference in 7.5 that requires a decrypt entry for connection to work?
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