E-PORTAL: Migration Of Portal Object Is Moving Security Of Objects Between Environments
(Doc ID 1924344.1)
Last updated on JULY 22, 2020
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.53 and later
Information in this document applies to any platform.
When copying Portal Object regardless of if you are using copy to database or file it seems that security (Roles and Permission Lists) associated with the objects are also migrated . This is potentially an issue when migrating from non-Prod to Prod environment where Roles and Permission List names may be the same but provide different access .
Issue can be replicated with the following steps :
1- Assign a custom Permission List to a Portal Object By cloning an existing Role or Permission List that grants access to that navigation in environment A
2- Create a new Project and insert the Portal object into the Project and save
3- Navigate to tools Copy Project to database and place in credentials for database B
4- Click on copy .
5- Environment B navigate to the portal object you inserted via Structure and Content
6- Note* new Permission List added under the "Security tab" of your content reference.
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