maria-developers team mailing list archive

["Vladislav Vaintroub" <wlad@xxxxxxxxxxxxxxxx>]

> -----Original Message-----
> From: Sergei Golubchik [mailto:serg@xxxxxxxxxxx]
> Sent: Sonntag, 14. Juli 2013 10:55
> To: Vladislav Vaintroub
> Cc: qiush.summer@xxxxxxxxx; maria-developers@xxxxxxxxxxxxxxxxxxx
> Subject: Re: Pluggable authentication, custom error messages
> 
> Hi, Vladislav!
> 
> On Jul 14, Vladislav Vaintroub wrote:
> > Hi Serg,
> > is there any possibility to return own error messages and codes , if
> > pluggable authentication failed on client on some reason ?
> >
> > Case in point here is Kerberos (GSSAPI or SSPI) - it may fail on client
or
> > on server, with some GSSAPI/SSPI specific code. We would like user to
> know
> > what exactly happened , rather than return a generic CR_ERROR.  Perhaps
> user
> > can fix the situation - maybe he just needs to obtain Kerberos ticket
with
> > kinit, or  login as Windows domain user, or something like that. If
error
> > happens on the server side, at least there it is possible to write to
error
> > log. But on the client side, there is no error log, and writing to
> > stdout/err is not a good idea.  Is there a trick that allows custom
messages
> > on the client?
> 
> On the server, I suppose, you can stil use my_error() and co.
> 
> On the client - libmysql uses set_mysql_extended_error() - is it
> exported to plugins? If yes - you're good. If not, we can, probably,
> export it.

Ok,  this already helps, thanks!

Re set_mysql_extended_error(), no, it is not exported at the moment (neither
in MYSQL_PLUGIN_VIO struct, nor as exported symbol from the shared lib) .  A
non perfect solution for just now (or until ABI changes)  would be filling
mysql->net.last_error, just like set_mysql_extended_error() does now.