Hi

Do you have any idea how we can enable logging into pgadmin4.2

For example. I want to track following.


1.       Login/logout logs  in pgadmin4 console

2.       Any new user id creation/deletion information




I  created the config_local.py under /var/log/pgadmin4 and restarted the apache 
using command (systemctl restart httpd)



#Contents of config_local.py



import logging

# Application log level - one of:

#   CRITICAL 50

#   ERROR    40

#   WARNING  30

#   SQL      25

#   INFO     20

#   DEBUG    10

#   NOTSET    0

CONSOLE_LOG_LEVEL = logging. WARNING

FILE_LOG_LEVEL = logging. WARNING



# Log format.

CONSOLE_LOG_FORMAT = '%(asctime)s: %(levelname)s\t%(name)s:\t%(message)s'

FILE_LOG_FORMAT = '%(asctime)s: %(levelname)s\t%(name)s:\t%(message)s'



LOG_FILE = '/var/log/pgadmin4/pgadmin4.log'

SQLITE_PATH = '/var/lib/pgadmin4/pgadmin4.db'

SESSION_DB_PATH = '/var/lib/pgadmin4/sessions'

STORAGE_DIR = '/var/lib/pgadmin4/storage'

DEFAULT_SERVER='XX.XX.XX.XX'

#DEFAULT_SERVER_PORT=443

Thanks,

Maulik Shah
EIO&T CTI Database Services
Citi Technology Center | Pune
SEZ-EON IT Park | Kharadi | Pune | Maharashtra - 411014 | INDIA
T +91 020-67098371
maulik.dipakkumar.s...@citi.com<mailto:maulik.dipakkumar.s...@citi.com>

From: [pgadmin.org] Dave Page <dp...@pgadmin.org>
Sent: Wednesday, June 12, 2019 5:57 PM
To: Shah, Maulik Dipakkumar [CCC-OT] <ms20...@imcap.ap.ssmb.com>
Cc: pgadmin-support@lists.postgresql.org
Subject: Re: How to disable the SSLv3 and TLS 1.0 and weak ciphers in pgAdmin 
4.1

Hi

Then you'll need to ask in a more appropriate place - we can't provide support 
for Apache HTTPD here; we're just users of it like you.

On Wed, Jun 12, 2019 at 1:22 PM Shah, Maulik Dipakkumar 
<maulik.dipakkumar.s...@citi.com<mailto:maulik.dipakkumar.s...@citi.com>> wrote:
Hi

This is already followed but not worked.

Thanks,

Maulik Shah

From: 
[pgadmin.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__pgadmin.org&d=DwMFaQ&c=j-EkbjBYwkAB4f8ZbVn1Fw&r=gNMyz7ZYrdmxsFDi4nZ_9n-tshD7S0kSmLgr4LBFV7w&m=46Mt_OMCpd_pvXh1FU2skO68S2R8-aGbykHWE7PsuwI&s=axeuJNoMf3uEYZMVM5ZbwRQVJg-n6mLq7pR_50K53JA&e=>]
 Dave Page <dp...@pgadmin.org<mailto:dp...@pgadmin.org>>
Sent: Wednesday, June 12, 2019 3:17 PM
To: Shah, Maulik Dipakkumar [CCC-OT] 
<ms20...@imcap.ap.ssmb.com<mailto:ms20...@imcap.ap.ssmb.com>>
Cc: 
pgadmin-support@lists.postgresql.org<mailto:pgadmin-support@lists.postgresql.org>
Subject: Re: How to disable the SSLv3 and TLS 1.0 and weak ciphers in pgAdmin 
4.1

Hi

On Wed, Jun 12, 2019 at 10:31 AM Shah, Maulik Dipakkumar 
<maulik.dipakkumar.s...@citi.com<mailto:maulik.dipakkumar.s...@citi.com>> wrote:
Hi Team

We have installed the pgAdmin 4.1 on RHEL 7 machine

Please advise how to disable the support for SSLv3 and TLS 1.0 using apache for 
pgAdmin 4.1

Could you please share some documentation on this. What would be the 
configuration in /etc/httpd/conf.d/SSL.conf

A quick Google gives me this: 
https://www.leaderssl.com/news/471-how-to-disable-outdated-versions-of-ssl-tls-in-apache<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.leaderssl.com_news_471-2Dhow-2Dto-2Ddisable-2Doutdated-2Dversions-2Dof-2Dssl-2Dtls-2Din-2Dapache&d=DwMFaQ&c=j-EkbjBYwkAB4f8ZbVn1Fw&r=gNMyz7ZYrdmxsFDi4nZ_9n-tshD7S0kSmLgr4LBFV7w&m=V1Cat2neid8zik8ltcqVVki1b8-_f-_jDiP8OBJlJis&s=aHIEwDQdJ2wtUg0ar134w3c2JaCOtRaOXc9HP6c9CPY&e=>

--
Dave Page
Blog: 
http://pgsnake.blogspot.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__pgsnake.blogspot.com&d=DwMFaQ&c=j-EkbjBYwkAB4f8ZbVn1Fw&r=gNMyz7ZYrdmxsFDi4nZ_9n-tshD7S0kSmLgr4LBFV7w&m=V1Cat2neid8zik8ltcqVVki1b8-_f-_jDiP8OBJlJis&s=-eXLYqEYes3Bg4-XV1opQA0jl7vSr4r68VdSspuCJaM&e=>
Twitter: @pgsnake

EnterpriseDB UK: 
http://www.enterprisedb.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.enterprisedb.com&d=DwMFaQ&c=j-EkbjBYwkAB4f8ZbVn1Fw&r=gNMyz7ZYrdmxsFDi4nZ_9n-tshD7S0kSmLgr4LBFV7w&m=V1Cat2neid8zik8ltcqVVki1b8-_f-_jDiP8OBJlJis&s=do71X3AbfayidG1pU6sIyuI4OOGtByjMOvy2q_AliYY&e=>
The Enterprise PostgreSQL Company


--
Dave Page
Blog: 
http://pgsnake.blogspot.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__pgsnake.blogspot.com&d=DwMFaQ&c=j-EkbjBYwkAB4f8ZbVn1Fw&r=gNMyz7ZYrdmxsFDi4nZ_9n-tshD7S0kSmLgr4LBFV7w&m=46Mt_OMCpd_pvXh1FU2skO68S2R8-aGbykHWE7PsuwI&s=WuI7RAuuEPziSIMZuLmtdl43ebiq64bZMjKaL_E6OWk&e=>
Twitter: @pgsnake

EnterpriseDB UK: 
http://www.enterprisedb.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.enterprisedb.com&d=DwMFaQ&c=j-EkbjBYwkAB4f8ZbVn1Fw&r=gNMyz7ZYrdmxsFDi4nZ_9n-tshD7S0kSmLgr4LBFV7w&m=46Mt_OMCpd_pvXh1FU2skO68S2R8-aGbykHWE7PsuwI&s=Mx2ibRW9isB1KXe5zKL0QRqkrYSN6csmoCl-4nv_bMk&e=>
The Enterprise PostgreSQL Company

Reply via email to