-
I've added following options:
omemo-identities-limit
- setting it to2
will enforce that only 2 nodes with OMEMO bundles can be createdomemo-unique-device-identity
- setting it totrue
will enforce that identity key for OMEMO device id cannot be changed
Example configuration:
pubsub () { 'item-validator' () { 'omemo-identities-limit' = 2 'omemo-unique-device-identity' = true } }
Type |
Task
|
Priority |
Normal
|
Assignee | |
Version |
tigase-server-8.5.0
|
Sprints |
n/a
|
Customer |
n/a
|
Iterations
-
tigase-server-8.5.0 Open
Issue Votes (0)
During normal operation OMEMO device identity key shouldn't be changed for the same device id. If would be good to be able to enforce that on the server side, to make sure that identity of a device will remain unchanged.
Additionally, it would be good to restrict no. of OMEMO identities/devices that can be used by a user at a single item.