My Oracle Support Banner

AVDF 20.4 DBFW POLICY DOES NOT WORK WITH TOAD WHEN USING OS USER SETS (Doc ID 2808101.1)

Last updated on SEPTEMBER 26, 2021

Applies to:

Oracle Audit Vault and Database Firewall - Version 20.4.0.0.0 and later
Information in this document applies to any platform.

Symptoms


1. Policy work fine when implemented through DB user set or IP sets for both 
 Toad and SQL Developer.  

2. Policy does not work if when implemented using 'OS User Sets'  
3. When using Toad, it shows OS username in 'All Activity Report' with domain name. i.e abc-xy\username
4. When using SQL Developer, it shows OS username in 'All Activity Report' without domain name. i.e username

   Including both OS usernames patterns (with and without domain),does not work. 

   Observation is when OS username has domain name within it, the issue encounters (might be due to special characters used in domain name like '\' 
   or '-'. 
 
 
   In AVDF 12.2, adding OS usernames with both patterns in OS User set and it works fine in 12.2 for both Toad and SQL Developer. 
 

Cause

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
Symptoms
Cause
Solution
References


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