#1983 Unable to set user role, set_jid_role not-implemented
Reporter
Sarah Valentine
Owner
Nobody
Created
Updated
Stars
★★ (2)
Tags
Priority-Medium
Status-New
Type-Defect
Sarah Valentine
on
What steps will reproduce the problem?
1. Create a MUC
2. Define custom roles within MUC
3. Use admin shell to assign a user a custom role within the MUC
What is the expected output?
Role is assigned as expected.
What do you see instead?
prosody> user:set_role("user@mydomainhere.com","muc.mydomainhere.com","my:role")
! Error: not-implemented
What version of the product are you using? On what operating system?
prosodyim/prosody:13.0 latest docker image on linux.
Please provide any additional information below.
mod_admin_shell.lua line ~2036 attempts to call um.set_jid_role because the user's host and the muc's host don't match. usermanger.lua ~351 calls authz's set_jid_role, mod_authz_internal.lua ~273 errors with "not-implemented".
Component "muc.mydomainhere.com" "muc"
modules_enabled = { "ogp","muc_mam" }
muc_log_expires_after = "1y"
custom_roles = {
{
name = "my:role";
inherits = { "prosody:member" };
};
What steps will reproduce the problem? 1. Create a MUC 2. Define custom roles within MUC 3. Use admin shell to assign a user a custom role within the MUC What is the expected output? Role is assigned as expected. What do you see instead? prosody> user:set_role("user@mydomainhere.com","muc.mydomainhere.com","my:role") ! Error: not-implemented What version of the product are you using? On what operating system? prosodyim/prosody:13.0 latest docker image on linux. Please provide any additional information below. mod_admin_shell.lua line ~2036 attempts to call um.set_jid_role because the user's host and the muc's host don't match. usermanger.lua ~351 calls authz's set_jid_role, mod_authz_internal.lua ~273 errors with "not-implemented". Component "muc.mydomainhere.com" "muc" modules_enabled = { "ogp","muc_mam" } muc_log_expires_after = "1y" custom_roles = { { name = "my:role"; inherits = { "prosody:member" }; };