Skip to content

Update OuaOverPipeReadme.md #844

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
gmaystro wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update OuaOverPipeReadme.md #844

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions filter-plugin/logstash-filter-oua-guardium/OuaOverPipeReadme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,10 +44,9 @@ Update the variables in Makefile for your environment's Java home and Logstash l
CREATE USER guardium IDENTIFIED BY password;
GRANT CONNECT to guardium;
GRANT SELECT ANY DICTIONARY to guardium;
GRANT AUDIT_VIEWER to guardium;
GRANT SELECT ON v$INSTANCE to guardium;
GRANT SELECT ON v$DATABASE to guardium;
GRANT SELECT ON v$MYSTAT to guardium;
GRANT SELECT ON v_$INSTANCE to guardium;
GRANT SELECT ON v_$DATABASE to guardium;
GRANT SELECT ON v_$MYSTAT to guardium;
```

- For other environments including RDS in AWS and Oracle Databases On-Premises run the following commands:
Expand Down Expand Up @@ -101,4 +100,4 @@ Update the variables in Makefile for your environment's Java home and Logstash l
## Limitation
- Normally, the "statement type" attribute for the "FULL SQL" entity in Guardium reports shows us whether a full SQL statement is a prepared statement. However, because OUA doesn't give us information about whether a statement is a prepared statement or not, the "Statement type" attribute is not applicable for the OUA universal connector plug-in.
- The "record affected" field is not supported when using Oracle with the universal connector.
- If you restart the database, then any Universal Connector that uses the OUA plugin must also be restarted.
- If you restart the database, then any Universal Connector that uses the OUA plugin must also be restarted.