Account Hierarchy does not Populate from LDAP Users, only the Top Level Populates, not the Lower Levels
(Doc ID 1939760.1)
Last updated on MAY 15, 2018
Applies to:Oracle WebCenter Content - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
After adding the fix from Note 1413490.1 which allows WebCenter Content to display accounts populated directly from LDAP groups, the top-lelvel accounts from the account hierarchy populate but the lower levels do not display.
When giving users access to the top level of Account Hierarchy the Checking Drop down does not display lower levels. for example:
When adding the user to a group in LDAP @TopLevelACCOUNT_RW it gives him write access to all 3 accounts based on the hierarchical account.
however, when checking in a document, the user can only select TopLevelACCOUNT from the list, it is expected to see all 3 accounts as he has access in all of them based on the hierarchy of accounts.
If a user is added to the lower levels directly. i.e. an LDAP group @TopLevelACCOUNT/A1_RW the A1 account is displayed correctly, however we do not want to have to create and maintain RW LDAP groups for every account in the system
Is this expected or is there some sort of workaround?
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