Mysql pluggable authentication and membership provider
Mysql pluggable authentication and membership provider
I was curious if devarts asp.net membership provider can be incorporated into mysql's pluggable authentication? If so, would you consider blogging about how to accomplish this task?
It should be possible to use pluggable authentication when connecting with the "Direct=false;" connection string parameter via dotConnect for MySQL (the corresponding libmysql.dll should support pluggable authentication): http://dev.mysql.com/doc/refman/5.5/en/ ... ation.html.
We will investigate the possibility of implementing the pluggable authentication support in the "Direct=true;" mode and notify you about the results as soon as possible.
We will investigate the possibility of implementing the pluggable authentication support in the "Direct=true;" mode and notify you about the results as soon as possible.
We have investigated the issue.
Pluggable Authentication via MySQL client library (Direct=false;) will be supported starting from the next build of dotConnect for MySQL. We have implemented two additional parameters to support this feature:
1) "PluginDir" - the directory where the plugin is located. This connection parameter is used to set MYSQL_PLUGIN_DIR option of MySQL client library.
2) "DefaultAuthPlugin" - the name of the authentication plugin to use. This connection parameter is used to set MYSQL_DEFAULT_AUTH option of MySQL client library. Usage of this option is not necessary because client finds out the name of the authentication plugin to use from server during handshake. This option allows to reduce the client/server negotiation and avoid a round trip in the protocol.
I will post here when the corresponding build of dotConnect for MySQL is available for download.
We do not have a technical possibility to support Pluggable Authentication in the direct mode at the moment.
Pluggable Authentication via MySQL client library (Direct=false;) will be supported starting from the next build of dotConnect for MySQL. We have implemented two additional parameters to support this feature:
1) "PluginDir" - the directory where the plugin is located. This connection parameter is used to set MYSQL_PLUGIN_DIR option of MySQL client library.
2) "DefaultAuthPlugin" - the name of the authentication plugin to use. This connection parameter is used to set MYSQL_DEFAULT_AUTH option of MySQL client library. Usage of this option is not necessary because client finds out the name of the authentication plugin to use from server during handshake. This option allows to reduce the client/server negotiation and avoid a round trip in the protocol.
I will post here when the corresponding build of dotConnect for MySQL is available for download.
We do not have a technical possibility to support Pluggable Authentication in the direct mode at the moment.
New build of dotConnect for MySQL 6.30.172 is available for download!
It can be downloaded from http://www.devart.com/dotconnect/mysql/download.html (trial version) or from Registered Users' Area (for users with valid subscription only): http://secure.devart.com/ .
For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=21278 .
It can be downloaded from http://www.devart.com/dotconnect/mysql/download.html (trial version) or from Registered Users' Area (for users with valid subscription only): http://secure.devart.com/ .
For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=21278 .