-
Problem report
-
Resolution: Fixed
-
Critical
-
5.0.30, 6.0.12, 6.2.6, 6.4.0beta4
-
None
-
None
-
RHEL 8.7
LTS 6.0
PgSQL 14.6
TSDB 2.8.1
OpenSSL 1.1.1 series
Agent2 6.0.14
-
Sprint 103 (Aug 2023)
-
1
Steps to reproduce:
- Follow: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/postgresql_agent2/README.md?at=refs%2Fheads%2Frelease%2F6.2
- Setup PgSQL server to use optional TLS (with mandatory we will just fail);
- Check PgSQL stats:
SELECT datname,usename, ssl, client_addr FROM pg_stat_ssl JOIN pg_stat_activity ON pg_stat_ssl.pid = pg_stat_activity.pid;
Result:
Suggested user will not use encryption.
Expected:
Able to set tls options for the plugin like:
Plugins.PostgreSQL.TLSConnect=required
This is not a feature request, this is a bug in design. Create official template, implement encryption, and they are cannot be used until you manually re-create the template to support {$PG.SESSION} variable in all keys.
- depends on
-
ZBXNEXT-8157 Accept both: session name and key parameters
- Closed