As technology, I should support Tenant support for users of same organization

[olivierlemee]

https://www.notion.so/cybnity/454-452f0645dd524fd1b57d07a68a368a3d

REQ_SEC_3 : TenantId support is implemented to allow notification of several users attached to a same company and/or solution infrastructure dedicated to a company The exchanges to multiple connected users of a same company (e.g security team authorized/connected on a dedicated solution instance receiving a transversal notification event on eventbus/tenantId/all/ or via eventbus/all/) are possible with total confidentiality (without possible visibility for other companies and/or infrastructures when solution is deployed on a Cloud/SaaS strategy).

ech: Vert.x Web; sockJS event bus bridge

upgrade fact repository and store persistence interface contract (immutable project) to support tenant id segregation according to the page 401 DDD book

[olivierlemee]

TODO:

• [x] ActivityState: rédiger TU des méthodes de création, test de isactive, equals, changement d'historique (new version desactivé)
• [x] rédiger TU de la méthode equals sur mutableproperty avec diverses equals ou non values en conteneur
• [x] AccessAccountDescriptor:
  • TU instantiation, création immutable (owner, tenant embarqués)
  • coder equals + TU du descriptor d'account
• [x] Unit test of SocialEntity, Person, OrganizationalStructure
• [x] TODO: UML documentation for access-control, and resolution of mermaid problem on framework page

[olivierlemee]

• Unit test of IdentifierStringBased; refactoring of equality methods (hashCode(), equals()) on domain and immutable objects
• ActivityState: unit test about constructor, isActive() life cycle, equals(), history enhancement with new version
• Tenant: setOrganization unit test

[olivierlemee]

Tenant: unit tests regarding activity state changes (activate/deactivate)

[olivierlemee]

repo and datastore, and ISessionContext evolution with tenant used

[olivierlemee]

domains and immutable packages uml documentation written