comparison mod_auth_cyrus/sasl_cyrus.lua @ 6319:04c3273cb81f

mod_auth_cyrus: Add empty 'profile' table to SASL handler objects This is for compatibility with Prosody's built-in util.sasl objects. A SASL profile table usually includes methods supported by the backend, which can be used by SASL mechanism handlers to perform operations (such as testing the password). It also optionally contains a 'cb' field with channel binding method handlers. The Cyrus backend doesn't support channel binding, and doesn't have the same concept of auth backend methods (it handles all that internally, and Prosody has no insight or control over it). Thus, we create an empty profile which informs Prosody that the SASL handler does not support any of the auth or channel binding methods. Some features will not work, but they didn't work anyway. This just makes it explicit. This fixes a traceback in mod_sasl2_fast, which expected SASL handlers to always contain a 'profile' field.
author Matthew Wild <mwild1@gmail.com>
date Thu, 04 Sep 2025 10:14:46 +0100
parents 099dcdb732b1
children
comparison
equal deleted inserted replaced
6318:07808fcda0e4 6319:04c3273cb81f
109 local cyrus_mechs = cyrussasl.listmech(sasl_i.cyrus, nil, "", " ", ""); 109 local cyrus_mechs = cyrussasl.listmech(sasl_i.cyrus, nil, "", " ", "");
110 for w in s_gmatch(cyrus_mechs, "[^ ]+") do 110 for w in s_gmatch(cyrus_mechs, "[^ ]+") do
111 mechanisms[w] = true; 111 mechanisms[w] = true;
112 end 112 end
113 sasl_i.mechs = mechanisms; 113 sasl_i.mechs = mechanisms;
114 sasl_i.profile = {};
114 return setmetatable(sasl_i, method); 115 return setmetatable(sasl_i, method);
115 end 116 end
116 117
117 -- get a fresh clone with the same realm and service name 118 -- get a fresh clone with the same realm and service name
118 function method:clean_clone() 119 function method:clean_clone()