Want this feature implemented, too? Please upvote by clicking Thumbs up!

(Posts as a reply won't be published in this feature request thread. Read Me!)

User Story

As a PRTG User, I want to use scram-sha-256 aus authentication method for PostgreSQL, but PRTG actually only supports AuthenticationClearTextPassword and AuthenticationMD5Password supported.

Details of User Story

Due to the regulations of BSI in Postgresql has to be changed the authentication method from MD5 to scram-sha-256, see: https://www.postgresql.org/docs/11/auth-password.html Because PRTG actually not supports scram-sha-256, we can't monitor PostgreSQL databases no more.

It's suprising, that this is the first feature request to that theme: PRTG uses MD5, which is due to BSI Basic Protection no more allowed since 2017

Acceptance criteria

  • support of scram-sha-256

Status

Open

Article Comments

I strongly support this.

It doesn't make sense that the monitoring system requires us to enable deprecated protocols which no real user ever will use.

A monitoring system that is accessing the monitored system via a different protocol (md5) than all the users (scram-sha-256) is nearly useless.

And as far as I understood the reason for this is the inclusion of an ancient version of the library from more than a decade ago (see https://helpdesk.paessler.com/en/support/solutions/articles/88969-prtg-should-use-newer-npgsql-dll).


Jun, 2021 - Permalink

Finally: Release 22.2.76.1705 updates the ancient library and henceforth allows us to use this sensor again.


Jun, 2022 - Permalink