VPD Predicate Not Applied on User_Preference Tables (Doc ID 2563648.1)

Last updated on DECEMBER 04, 2019

Applies to:

Symptoms

Custom VPD Predicate to restrict users to update User Preferences which were not created by themselves, is not effective.

TEST CASE
--------------
User ID: <DOMAIN_NAME>.USER01

Created User Preference ID: VPD User Preference

select * from USER_PREFERENCE where USER_PREFERENCE_GID='<DOMAIN_NAME>.VPD USER PREFERENCE'

INSERT_USER
<DOMAIN_NAME>.USER01

Created VPD Profile: VPD User Preference

USER_PREFERENCE.insert_user = sys_context('gl_user_ctx', 'LOG_IN_USER_GID')
USER_PREFERENCE_D.insert_user = sys_context('gl_user_ctx', 'LOG_IN_USER_GID')

Now login as <DOMAIN_NAME>.USER02
Switch the User Role to (VPD USER PREFERENCE) > this has the VPD Profile assigned.

Now click on the user ID <DOMAIN_NAME>.USER02 > then click "User Preferences" under the "Administration" section

Now, if you click on the User preferences, OTM will open up the (VPD USER PREFERENCE) User Preference. Make a change and save.

You will see the following in the DB. The Insert User (<DOMAIN_NAME>.USER01), the Update User (<DOMAIN_NAME>.USER02)

USER_PREFERENCE_GID USER_PREFERENCE_XID DOMAIN_NAME INSERT_USER INSERT_DATE UPDATE_USER UPDATE_DATE
<DOMAIN_NAME>.VPD USER PREFERENCE VPD USER PREFERENCE <DOMAIN_NAME> <DOMAIN_NAME>.USER02 2019-05-20 20:57:38.0 <DOMAIN_NAME>.USER02 2019-05-21 22:53:40.0

Cause

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