No logging of database authentication errors

Bug #672130 reported by Tristan Hill
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Odoo Server (MOVED TO GITHUB)
Fix Released
Low
OpenERP's Framework R&D

Bug Description

Steps to reproduce
 * start a server with incorrect db username or password but without specifying a database name
   e.g. python ~/src/openerp-trunk/server/bin/openerp-server.py --db_user invalid
 * connect to server with client

Expect
 * error message on server to indicate database authentication error

Actual
 * no error on server

With current latest trunk.

Revision history for this message
Olivier Dony (Odoo) (odo-openerp) wrote :

You're right, we'll see if there is an easy way to add this, thanks for suggesting!

summary: - no database authentication error
+ No logging of database authentication errors
Changed in openobject-server:
importance: Undecided → Low
milestone: none → 6.0-rc2
status: New → Confirmed
Changed in openobject-server:
assignee: nobody → OpenERP's Framework R&D (openerp-dev-framework)
Changed in openobject-server:
status: Confirmed → In Progress
Revision history for this message
xrg (xrg) wrote :

[2010-11-29 20:12:03] INFO:web-services:bad login or password from 'admin' using database 'test_bqi'

That's the message that has been in the server for quite many months already. The level is "info", rather than "error", on purpose: repeated failed attempts should not fill the logs (DoS by logs).

Revision history for this message
Olivier Dony (Odoo) (odo-openerp) wrote :

The fix has landed in trunk with revision 3055 <email address hidden>
Thanks for reporting!

Changed in openobject-server:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.