E1: SEC: Column Security on Multiple Roles for *ALL Objects not Applied Correctly on Web Client (Doc ID 1271589.1)

Last updated on MAY 30, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 to 8.98 [Release 8.98]
Information in this document applies to any platform.

Symptoms

When column security is defined for a specific data item for *ALL objects on a role with a higher sequence number than another role with column security defined for a different data item either for *ALL objects or for a specific object, the column security defined for the role with the lower sequence number is ignored and not applied. 

If the column security defined for *ALL objects is for a role with a lower sequence than another role with column security on a different data item, the column security is applied for both roles as expected.

Steps to Duplicate:

  1. Add two roles (ROLE01, ROLE02) with ROLE02 having a higher sequence number than ROLE01
  2. Add the following column security
    • ROLE01 - object P0092, data item AN8 and View(N), Add(N), Change(N)
    • ROLE02 - *ALL object, data item USR0 and View(N),Add(N),Change(N)
  3. On the Web client, column security is Not applied for ROLE01 in P0092.  Column security is applied for ROLE02 in P9830.
  4. Change the role sequencing so that ROLE1 has the higher sequence number.
  5. Now on the web client, the column security is applied for both roles as expected.

The column security is correctly applied on the Fat client regardless of the role sequence number.  This is only an issue on the Web client.  The OWWEB setting useRoleHierarchy=true is in the jas.ini.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms