Fixing a SASL issue by always passing the realm from SASL framework init to the handlers.

Sat, 08 Aug 2009 21:13:18 +0200

author
Tobias Markmann <tm@ayena.de>
date
Sat, 08 Aug 2009 21:13:18 +0200
changeset 1656
cf9220a364cd
parent 1642
8ba5752851dc
child 1657
1fe566011e2b

Fixing a SASL issue by always passing the realm from SASL framework init to the handlers.

util/sasl.lua file | annotate | diff | comparison | revisions
--- a/util/sasl.lua	Fri Aug 07 11:32:47 2009 +0100
+++ b/util/sasl.lua	Sat Aug 08 21:13:18 2009 +0200
@@ -198,7 +198,7 @@
 
 			--TODO maybe realm support
 			self.username = response["username"];
-			local password_encoding, Y = self.credentials_handler("DIGEST-MD5", response["username"], to_unicode(domain), response["realm"], decoder);
+			local password_encoding, Y = self.credentials_handler("DIGEST-MD5", response["username"], self.realm, response["realm"], decoder);
 			if Y == nil then return "failure", "not-authorized"
 			elseif Y == false then return "failure", "account-disabled" end
 			local A1 = "";

mercurial