diff --git a/VERSION b/VERSION
index e3d360b..174ad37 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-0.1-10.4
+0.2-10.4
diff --git a/load_pam_plugin.cnf b/load_pam_plugin.cnf
index 76d9b5e..36cc368 100644
--- a/load_pam_plugin.cnf
+++ b/load_pam_plugin.cnf
@@ -1,4 +1,13 @@
 [mariadb]
-plugin_load=auth_pam.so
+plugin_load=auth_pam
+pam_use_cleartext_plugin = ON
+
+# create these stuff and enable the following configuration
+# otherwise the pam_use_cleartext_plugin won't work which
+# is required for dotnet connections
+# ssl_cert = /etc/mysql/conf.d/ssl/server-cert.pem
+# ssl_key = /etc/mysql/conf.d/ssl/server-key.pem
+# ssl_ca = /etc/mysql/conf.d/ssl/ca.pem
+
 
 
diff --git a/readme.md b/readme.md
index abf450d..fba4355 100644
--- a/readme.md
+++ b/readme.md
@@ -25,4 +25,16 @@ Start the container after creating the required volumes (see documentation of th
       -e MYSQL_ROOT_PASSWORD=test123 \
       wollud1969/mariadb-with-ldap-pam:latest
 
+Since one important scenario in my environment is access from dotnet applications, where the client plugin dialog is not available (https://mariadb.com/kb/en/library/authentication-plugin-pam/#using-the-plugin-with-mysqlconnector-for-net), I've add the configuration line
+
+    pam_use_cleartext_plugin = ON
+
+to the default configuration. This in turn requires SSL/TLS connections to the database server so I added the SSL configuration to the default config file.
+
+To enable users to access the database server with PAM/LDAP authentication, you still need to create those users in the database:
+
+    CREATE USER username@hostname IDENTIFIED VIA pam USING 'mariadb';
+
+For details see https://mariadb.com/kb/en/library/authentication-plugin-pam/
+