In most Oracle WebCenter Content environments, one person ends up owning every security mapping change. A department reorganizes, a new plant comes online, a job code is renamed, and the request lands on the WebCenter administrator, because nobody else is allowed to touch the rules. The rules are not hard to change. The bottleneck is who has permission to change them.
Version 9.5 of Advanced User Security Mapping for Oracle WebCenter Content is built around that problem.
What is new in 9.5
Delegated rule editing. You can now let configurable non-admin roles edit the conditions of designated mapping rules. The administrator decides which rules are open to delegation and which roles may edit them. Everything else stays locked. The person who knows which job codes belong to a department can keep that rule current without being handed administrator rights.
Filter and reorder from the rules list. Mapping rules can be filtered and reordered directly from the list, which matters once a rule set grows past a few dozen entries.
A faster rules page. Performance of the current mapping rules page is improved.
Fixes worth knowing about
Version 9.5 corrects a case where Evaluate User Permissions could disagree with the results of Retrieve Users with Access. If you rely on those two tools to answer an auditor asking who can see a document and why, they now tell the same story. The release also fixes an error when saving organizational unit rules and a null pointer exception tied to role validation.
If you are a few versions behind
Recent releases added more than 9.5 alone:
- WebCenter Content 14c certification arrived in 9.3.
- Credential map information in user evaluation results, stronger rule validation, and an updated expression library arrived in 9.4.
- Configuration history that records who made each change arrived in 9.2.
One change to plan for
Rule ordering has moved from the priority setting to a RuleOrder configuration object. Review the product documentation before you upgrade so your rule order carries over as you expect.
Why this matters
Security mapping is where least privilege either holds or erodes. When only an administrator can update a rule, changes queue up, and the workaround is usually to grant broader access than anyone intended. Delegating a specific rule to the person who owns that decision keeps access accurate without widening who holds admin rights, and the configuration history shows who changed what.
Getting the release
Customers with current maintenance can request version 9.5 from Fishbowl Support at support.fishbowlsolutions.com. If you are evaluating Advanced User Security Mapping, request a demo and we will walk through delegated rule editing against your own directory structure.