prosody: use hashed xmpp auth

Author: bgrozev

prosody/rootfs/defaults/conf.d/jitsi-meet.cfg.lua

@@ -33,7 +33,7 @@ VirtualHost "{{ .Env.XMPP_DOMAIN }}"
     cyrus_application_name = "xmpp"
     allow_unencrypted_plain_auth = true
   {{ else if eq $AUTH_TYPE "internal" }}
-    authentication = "internal_plain"
+    authentication = "internal_hashed"
   {{ end }}
 {{ else }}
     authentication = "anonymous"
@@ -67,14 +67,14 @@ VirtualHost "{{ .Env.XMPP_AUTH_DOMAIN }}"
         key = "/config/certs/{{ .Env.XMPP_AUTH_DOMAIN }}.key";
         certificate = "/config/certs/{{ .Env.XMPP_AUTH_DOMAIN }}.crt";
     }
-    authentication = "internal_plain"
+    authentication = "internal_hashed"
 
 {{ if .Env.XMPP_RECORDER_DOMAIN }}
 VirtualHost "{{ .Env.XMPP_RECORDER_DOMAIN }}"
     modules_enabled = {
       "ping";
     }
-    authentication = "internal_plain"
+    authentication = "internal_hashed"
 {{ end }}
 
 Component "{{ .Env.XMPP_INTERNAL_MUC_DOMAIN }}" "muc"

prosody/rootfs/defaults/prosody.cfg.lua

@@ -126,7 +126,7 @@ s2s_secure_auth = false
 -- server please see http://prosody.im/doc/modules/mod_auth_internal_hashed
 -- for information about using the hashed backend.
 
-authentication = "internal_plain"
+authentication = "internal_hashed"
 
 -- Select the storage backend to use. By default Prosody uses flat files
 -- in its configured data directory, but it also supports more backends