[pgpool-hackers: 3597] Do we want to change successfull authentication log priority?
Tatsuo Ishii
ishii at sraoss.co.jp
Sat Apr 25 20:16:09 JST 2020
Recently we have multiple complains from users about successfull
authentication log.
https://www.pgpool.net/mantisbt/view.php?id=606
https://www.pgpool.net/pipermail/pgpool-general/2020-April/007064.html
Currently each time when Pgpool-II succeeds with client
authentication, following log is out:
pool_auth.c- {
pool_auth.c: ereport(LOG,
pool_auth.c- (errmsg("using clear text authentication with frontend"),
--
pool_auth.c- {
pool_auth.c: ereport(LOG,
pool_auth.c- (errmsg("using clear text authentication with frontend"),
--
pool_auth.c- }
pool_auth.c: ereport(LOG,
pool_auth.c- (errmsg("clear text authentication successful with frontend")));
--
pool_auth.c- frontend->frontend_authenticated = true;
pool_auth.c: ereport(LOG,
pool_auth.c- (errmsg("SSL certificate authentication for user \"%s\" with Pgpool-II is successful", frontend->username)));
--
pool_auth.c- frontend->frontend_authenticated = false;
pool_auth.c: ereport(LOG,
pool_auth.c- (errmsg("SSL certificate authentication for user \"%s\" failed", frontend->username)));
--
pool_auth.c- }
pool_auth.c: ereport(LOG,
pool_auth.c- (errmsg("md5 authentication successful with frontend")));
These flood out Pgpool-II log. I think they are too verbose and should
be downgraded to DEBUG1. Any objection?
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
More information about the pgpool-hackers
mailing list