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.

---
labels:
- 'Stage-Obsolete'
summary: Limit who may send and recieve MUC PMs
...

::: {.alert .alert-warning}
This feature has been merged into
[mod_muc][doc:modules:mod_muc] in trunk and is therefore obsolete when used with a version >0.12.x or trunk.
It can still be used with Prosody 0.12.
:::

# Introduction

This module adds configurable MUC options that restrict and limit who may send MUC PMs to other users.

If a user does not have permissions to send a MUC PM, the MUC will send a policy violation stanza.

# Setup

```lua
Component "conference.example.org" "muc"

modules_enabled = {
	"muc_restrict_pm";
}
```

Compatibility
=============

  version   note
  --------- ---------------------------------------------------------------------------
  trunk     [Integrated](https://hg.prosody.im/trunk/rev/47e1df2d0a37) into `mod_muc`
  0.12      Works