Primary Note for Configuring External Database Encryption and Related Issues in P6 EPPM Release 17 and Later
(Doc ID 2990466.1)
Last updated on DECEMBER 13, 2023
Applies to:Primavera P6 Enterprise Project Portfolio Management - Version 18.104.22.168 and later
Information in this document applies to any platform.
This document describes the internal and external database encryption methods available in P6 EPPM, and provides a list of existing Knowledge articles for some common encryption-related issues.
By default, P6 EPPM uses AES Encryption/Decryption to store and read various database and integration passwords (for example, the private database user password in the PUBUSER table or the public username password stored in the BREBootStrap.xml / PrmBootStrapV2.xml configuration files). In P6 EPPM release 16 and older versions, all encryption/decryption calls utilized encryption/decryption keys stored directly in the P6 codebase as obfuscated static strings.
Starting with release 17, P6 EPPM also includes the option for customers to create unique external encryption/decryption keys for a new or existing database using their own certificate.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!