Add OMEMO identities restrictions enforcer (#139)

In QA

Activities

Andrzej Wójcik (Tigase) opened 4 months ago

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.

Andrzej Wójcik (Tigase) added "Related" Customers/Bridge#3 4 months ago

Andrzej Wójcik (Tigase) changed state to 'In Progress' 4 months ago

Previous Value	Current Value
Open	In Progress

Referenced from commit 4 months ago

Added option to enforce OMEMO restrictions #139

Andrzej Wójcik (Tigase) committed 4 months ago

e585c844

Andrzej Wójcik (Tigase) commented 4 months ago

I've added following options:

omemo-identities-limit - setting it to 2 will enforce that only 2 nodes with OMEMO bundles can be created
omemo-unique-device-identity - setting it to true 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
    }
}

Andrzej Wójcik (Tigase) changed state to 'In QA' 4 months ago

Previous Value	Current Value
In Progress	In QA

Type	Task
Priority	Normal
Assignee	Andrzej Wójcik (Tigase)
Version	tigase-server-8.5.0
Sprints	n/a
Customer	n/a

Iterations

tigase-server-8.5.0 Open

Customers/Bridge#3 You are not authorized to access this issue

Issue Votes (0)

Watchers (3)

Reference

tigase/_server/tigase-pubsub#139