> -----Original Message-----
> From: Sergei Golubchik [mailto:serg@stripped]
> Sent: 19 May 2008 18:15
> On May 18, Guus Leeuw jr wrote:
> > Hello,
> > Sorry for the somewhat wide distribution, first of all.
> > (This message was originally cross-posted to
> > so please reply to them as well.)
> > Background:
> > I am implementing multiple websites using MySQL as a backend
> database. So
> > far, nothing new. However some of these websites will host
> applications that
> > are password protected and user-role authorized. Thus it would seem
> ideal if
> > we could somehow manage for the website password to be the same as
> > database password, so that we can target specific tables / databases
> > specific users. One of the databases is to hold financial data, which
> > would not want a "role-based" user id (aka "web"/"web") to be able to
> > I *assume* that a possibility like this would greatly benefit several
> > organizations using MySQL for similar purposes, if these
> > already have centralized password databases. Nowadays with Microsoft
> > supporting Kerberos by default as the means to store Active Directory
> > passwords, it would seem to me that a large number of organizations
> > fit that bill.
> The first thought is - check Summer of Code projects: there're two
> this is your roles.
OK, is Milos on the list? Are there already thoughts on the design, etc.
I don't really want to wait until after the Summer (sic) for this to be
Also, I kinda need it for 5.0, not 6.0 or something higher up the tree.
The easiest thing to do would then simply be to support SASL in MySQL, and
leave everything up to SASL.
(CRAM, DIGEST, GSSAPI, Auxprop, PAM)
[snipped as the discussion takes a turn towards pluggable authentication]