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-Beta'
summary: Automatically populate vcard based on account details
...

Introduction
============

It is possible for the user to supply more than just a username and
password when creating an account using
[mod\_register](https://prosody.im/doc/modules/mod_register). This
module automatically copies over that data to the user's vcard.

Details
=======

There is no configuration for this module, just add it to
modules\_enabled as normal.

Note that running this on a public-facing server that prompts for email
during registration will make the user's email address publicly visible
in their vcard.

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

  ----- -------
  0.9   Works
  ----- -------