367836 - Let the shadowdb connection have its own username and password

Status: RESOLVED FIXED

(Webtools Graveyard :: Bonsai, defect)

Description

[Dave Miller [:justdave]]

Should have done it this way to begin with...  it's only proper to lock down access on the shadow database so that the connection *can't* be used to write to the database.  In a fully replicated environment (where the privileges get replicated, too), the only way to do this is to set up a separate username that has the restricted privs, and use that username for the shadow database connection.  I did this during the troubleshooting to find out what was writing to the shadowdb in bug 367823, so I could get logged error messages with line numbers and query info when it failed.

Comment 1

[Dave Miller [:justdave]]

Attachment: Patch v1

Comment 2

[Reed Loden [:reed]]

Comment on attachment 252433 [details] [diff] [review]
Patch v1

ConnectToDatabase() needs to pick the correct mysql-related variables based on what dbiparam is chosen. Currently, if shadowdbiparam is empty, it falls back to dbiparam but tries to use shadowmysqluser and shadowmysqlpassword.

Comment 3

[Dave Miller [:justdave]]

Attachment: Patch v2

Good catch!

Comment 4

[Dave Miller [:justdave]]

Checking in defparams.pl;
/cvsroot/mozilla/webtools/bonsai/defparams.pl,v  <--  defparams.pl
new revision: 1.12; previous revision: 1.11
done
Checking in globals.pl;
/cvsroot/mozilla/webtools/bonsai/globals.pl,v  <--  globals.pl
new revision: 1.49; previous revision: 1.48
done