Sitedetout - Tutoriels informatiques

New security configuration flag in UCM PS3

New security configuration flag in UCM PS3

While the recent Patch Set 3 (PS3) release was mostly focused on bug fixes and such, a new configuration flag was added for security.


In 10gR3 and prior versions, UCM had a component called Collaboration Manager which allowed for project folders to be created and groups of users assigned as members to collaborate on documents. With this component came access control lists (ACL) for content and folders. Users could assign specific security rights on each and every document and folder within a project. And it was possible to enable these ACL’s without having the Collaboration Manager component enabled. But it took some special instructions (see technote# 603148.1) and added some extraneous pieces still related to Collaboration Manager.When 11g came out, Collaboration Manager was no longer available. But the configuration settings to turn on ACLs were still there. Well, in PS3 they’ve been cleaned up a bit and a new configuration flag has been added to simply turn on the ACL fields and none of the other collaboration bits.

To enable ACLs:


Along with this configuration flag to turn ACLs on, you also need to define which Security Groups will honor the ACL fields. If an ACL is applied to a content item with a Security Group outside this list, it will be ignored.


Save the settings and restart the instance. Upon restart, two new metadata fields will be created: xClbraUserList, xClbraAliasList. If you are using OracleTextSearch as the search indexer, be sure to run a Fast Rebuild on the collection.

On the Check In, Search, and Update pages, values are added by simply typing in the value and getting a type-ahead list of possible values.

User Typeahead

Select the value, click Add and then set the level of access (Read, Write, Delete, or Admin). If all of the fields are blank, then it simply falls back to just Security Group and Account access.

ACL Metadata Values

As for how they are stored in the metadata fields, each entry starts with it’s identifier: ampersand (&) symbol for users, “at” (@) symbol for groups, and colon (:) for roles. Following that is the entity name. And at the end is the level of access in paranthesis. e.g. (RWDA). And each entry is separated by a comma.So if you were populating values through batch loader or an external source, the values would be defined this way.

Detailed information on Access Control Lists can be found in the Oracle Fusion Middleware System Administrator’s Guide for Oracle Content Server.

Laisser un commentaire

Votre adresse e-mail ne sera pas publiée.

Menu Title

Powered by