[MDEV-18660] mariadb audit did not audit the connect message from Mysql workbench Created: 2019-02-20  Updated: 2023-05-30  Resolved: 2023-05-30

Status: Closed
Project: MariaDB Server
Component/s: Plugin - Audit
Affects Version/s: 10.2.14
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: yongjian.wu Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Environment:

linux 3.10.0-514.26.2.el7.x86_64
5.5.5-10.2.14-MariaDB

Attachments: Text File test case.txt    

 Description   

Hi
When we use the MySQL workbench to connect the Maria DB by Proxy SQL the audit message just have the "Query" but not "CONNECT" or "DISCONNECT",but if we connect the database directly the "CONNECT" or "DISCONNECT" and be audited.
After we test maybe is cause by the protocol type,and i have already upload the test case please have a check.Thank you .

 Comments   
Comment by yongjian.wu [ 2019-03-20 ]

Hi,i found another issue,when i use the mariadb10.3.13,use the "\s" and then quit the mariadb across the proxysql,the server_audit.log will have below output,hope you can take a look

20190320 11:57:20,localhost.localdomain,jian,192.168.135.191,18,0,CONNECT,information_schema,,0
20190320 11:57:20,localhost.localdomain,jian,192.168.135.191,18,31,QUERY,information_schema,'SET NAMES utf8mb4 COLLATE \'utf8mb4_general_ci\'',0
20190320 11:57:20,localhost.localdomain,jian,192.168.135.191,18,32,QUERY,information_schema,'select DATABASE(), USER() limit 1',0
20190320 11:57:20,localhost.localdomain,jian,192.168.135.191,18,33,QUERY,information_schema,'select @@character_set_client, @@character_set_connection, @@character_set_server, @@character_set_database limit 1',0
20190320 11:57:23,localhost.localdomain,OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO

Comment by Ralf Gebhardt [ 2023-04-24 ]

yongjian.wu, can you do us a favor and test this with a current version? An issue as mentioned in your comment was fixed a while ago

Generated at Thu Feb 08 08:45:47 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.