view doc/jp/account.rst @ 3104:118d91c932a7

plugin XEP-0384: OMEMO for MUC implementation: - encryption is now allowed for group chats - when an encryption is requested for a MUC, real jids or all occupants are used to encrypt the message - a cache for plain text message sent to MUC is used, because for security reason we can't encrypt message for our own device with OMEMO (that would prevent ratchet and break the prefect forward secrecy). Thus, message sent in MUC are cached for 5 min, and the decrypted version is used when found. We don't send immediately the plain text message to frontends and history because we want to keep the same MUC behaviour as for plain text, and receiving a message means that it was received and sent back by MUC service - <origin-id> is used to identify messages sent by our device - a feedback_jid is now use to use correct entity for feedback message in case of problem: with a room we have to send feedback message to the room and not the the emitter - encryptMessage now only accepts list in the renamed "entity_bare_jids" argument
author Goffi <goffi@goffi.org>
date Mon, 30 Dec 2019 20:59:46 +0100
parents 72583524cfd3
children
line wrap: on
line source

================================
account: XMPP account management
================================

``account`` command help you to create or manage the XMPP account of a server, using
In-Band Registration (`XEP-0077`_).

.. _XEP-0077: https://xmpp.org/extensions/xep-0077.html

create
======

Create a XMPP account. You have to specify your jid and password as positional arguments.
By default the registration is done on ``localhost`` with default XMPP Client 2 Server
port (i.e. 5222), but you can specify other host/port using ``-H HOST, --host HOST`` and
``-P PORT, --port PORT``. You may also specify an e-mail address using ``-e EMAIL, --email
EMAIL`` (use of this data depend of the server implementation).

By default, no SàT profile is created and associated to this new XMPP account, but you can
use ``-p PROFILE, --profile PROFILE`` if you are willing to have one.

example
-------

Create account for the new user Nestor at ``nestor@example.org`` and associate it with the
SàT profile ``nestor``::

  $ jp account create nestor@example.org some_password -p nestor


modify
======

Modify an existing XMPP account password. This will modify the XMPP account linked to the
given profile.

.. note::

   Only the XMPP password on the server is changed, not the one registered in the
   parameter of SàT. You may have to update the parameter of your profile if the new
   password doesn't correspond to your parameters one (you can do that with jp param set
   or with most SàT frontends in parameters).

example
-------

Change the XMPP password of the XMPP account of the default profile::

  $ jp account modify new_password


delete
======

Delete the XMPP account linked to the given profile from the XMPP server. Before using
this command, please be sure to understand well that **THIS WILL REMOVE THE WHOLE XMPP
ACCOUNT AND DATA FROM THE XMPP SERVER**.

By default a confirmation is requested, you can do this without confirmation by using
``-f, --force``, however this is **NOT RECOMMENDED**, be sure to understand what you're
doing if you use this option (and be sure to spell correctly the profile, if you forget
the ``-p PROFILE, --profile`` argument for instance, this would delete entirely the
default profile).

.. note::

   Be extra careful with this command, as it will remove the whole account from the
   server, and the associated data.

example
-------

Delete the XMPP account of Pierre, which is not on the local server anymore::

  $ jp account delete -p pierre