Last Modified: Jun 28, 2025
Affected Product(s):
BIG-IP DNS, GTM, LTM
Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4
Fixed In:
17.5.0, 17.1.2, 16.1.6
Opened: Jul 14, 2020 Severity: 1-Blocking
If a Postgresql server is configured to use the SCRAM-SHA-256 authentication method and configured as an LTM or GTM pool member, an LTM or GTM postgresql monitor will mark the pool member DOWN.
You will be unable to use a postgresql monitor to monitor the health of the Postgresql server
-- Postgresql server is configured to use the SCRAM-SHA-256 authentication method -- Postgresql server is configured as an LTM or GTM pool member -- The pool/member is configured to use an LTM or GTM postgresql monitor
To work around this issue, configure the Postgresql server to use MD5 authentication.
Monitor uses PostgreSQL JDBC driver upgraded to 42.2.13 via ID940317. For more information see: https://support.f5.com/csp/article/K23157312