Propagating Permissions for Folders and Files Doesn't Work Consistently or Returns Errors in WebCenter Portal 12c (Doc ID 2694405.1)

Last updated on NOVEMBER 01, 2022

Applies to:

Symptoms

ACTUAL BEHAVIOR

Propagating Permissions for Folders and Files Doesn't Work Consistently or Returns Errors in WebCenter Portal 12c.


EXPECTED BEHAVIOR

Expect permissions to be propagated properly.

STEPS

There are different scenarios to reproduce this issue. 

Use Case 1 - Unable to Propagate Permissions with a user who is not a content server administrator user  

Having a folder / subfolder structure with files as follows: 

    ParentFolder
        |
        +------> Subfolder
        |                 |
        |                 +--> file2
        |
        +------>file1

Action: Propagate permissions from the ParentFolder.

See success message:
You successfully propagated the selected field values to the contents of 'ParentFolder'.

Actual Results:

- For a user with Content Server Administration permissions: The permissions are applied down the tree.
- For a standard user (e.g. a Portal Manager / Owner of a Portal in WebCenter Portal) : The permissions are not propagated. 

Use Case 2 : Propagate Folder Option wipes out all permissions from all sub-folders/files down the tree 

When propagating permission from a Folder the Propagate window opens with empty ACLs.
If you apply changes it wipes out all permissions from all sub-folders/files down the tree. 

Use Case 3: ACLs are Not Updated in the Folder Metadata if Updating Folder Permissions 

Having a folder / subfolder structure as follows:

   Parent Folder
       |
      +------>Subfolder

Actions:

• • Propagate permissions from ParentFolder to Subfolder.
    
    
  • Update permissions on Subfolder (e.g. remove a user from ACLs) and save changes.
    
    

Actual Results:

• • Open the Subfolder properties and confirm the deleted user is no longer in the Security Tab.
    
    
  • Select the Metadata Tab for Subfolder.
    
    Here you will see the original permissions remain in the Folder Metadata.
    e.g., the deleted user still shows here. 

Use Case 4: "Inhibit propagation of security values trough this folder" does not work

Having a folder / subfolder structure with files as follows:

   ParentFolder
       |
       |
       +------> SubFolder1
       |                 |
       |                 +---------> SubFolder1_1
       |                 |                     |
       |                 |                     + -----------> FileB.docx
       |                 |
       |                 +---------> FileA.docx
       |
       +------> SubFolder2
       |                 |
       |                 +--------->SubFolder2_1
       |                 |                    |
       |                 |                    + ----------->File5.docx
       |                 |
       |                +---------> File4.docx
       |
       +------> File1.docx

Actions: 

• • Set custom permissions in the ParentFolder.
    
    
  • Propagate permissions from the ParentFolder so all subfolders and files inherit same security.
    
    
  • Set the following option in the Metadata Tab of SubFolder2:
    
    Inhibit propagation of security values trough this folder
    
    
  • Propagate new permissions from the ParentFolder.

Actual Results: 

• • You will get the following error:
    
    Errors occurred while attempting to propagate the selected field values to the contents of 'ParentFolder'.
    The operation was not completed.
    
    In the error message click on "Show Details".
    
    It will show the following details of the error:
    
    Confirmation Metadata was propagated to 7 items.
    
    Error SubFolder2_1: A null value cannot be propagated for field 'xIdcProfile'.
    
    Error file4.docx: Unknown error (!csUnableToUpdateInfo,WCPVMORACLECOM002257!csCheckinTitleRequired)
    
    
    
  • Check permissions on SubFolders and files and found all permissions are not propagated correctly.
    For example:
    
    SubFolder2 - Permissions were propagated to the folder.
    This is unexpected as the folder has the "Inhibit propagation of security values trough this folder" flag.
    
    SubFolder2_1 - Permissions were propagated to the folder.
    This is unexpected as SubFolder2 has the "Inhibit propagation of security values trough this folder" flag.
    
    File4.docx - Permissions were NOT propagated to the file.
    This was expected. 

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.