Open olivierlemee opened 1 year ago
evaluation of UX/UI design cost requested for tenant and account registration, sign-up, home
key events serialization and adaptation over UIS (redis) from access-control domain backend to UI Capabilities gateway
créer composant gateway (application domain IO module) AccessControlIOGateway
DONE: process de délégation issue des entrées globale dans le module RTS et déclenchement du process module (embarqué ou délégué vers un autre stream redis) en charge d'implémenter les règles avec keycloack/la couche métier envers l'aggrégat...) : vertx worker implémenté côté reception des recipients list
DONE préparation du projet de composant server Access Control Process Module (normalement écoutant toutes les demandes de capacités d'UI, comme gestionnaire de déploy verticle) qui intègre/déploy en interne des Verticles dédiés et embarqués gérant chaque capabilité spécifique (externalizable ultérieurement en modules vertx server indépendants implémentés des ac-service (services applicatifs) packagées en verticles. Normalement ce process module devrait être en écouté depuis kafka lorsque le io gateway de AC saura faire du routage des recipients reçus vers kafka (plutôt que vers des topics redis comme actuellement)
DONE: first feature (tenant registration) processing unit and common reusable classes (by any domain IO gateway, any domain feature processing unit) and collaboration functions regarding the implementation of Dynamic recipient routing list (routes between UI layer gateway > UI capability features) are developed.
DONE: dynamic routing between domain IO gateway and Feature modules over the UIS space (Redis) with unit test validating the first functional implementation (by AC IO domain gateway realizing the domain routing/delegation + TenantRegistration feature module realizing the registration pipeline) reusing the common components developed into the framework
DONE: generic extension of process module and pipeline module functions (e.g regarding all the collaboration, instantiation, configuration methods and behaviors) into common classes + refactoring of RTS module of access control as first impl + unit test validating with success the integration model
DONE: structure of registration service, tenants read model repository, tenants write model store and standardized coupling. Unit test preparation regarding organization registration scenario according to requirements
DONE: tenant registration service process coding according to the design model
DONE:
DONE:
DONE
DONE
DONE
FTEST_198: https://www.notion.so/cybnity/198-6dde495085b94fb3a1e4ee01d46b4d44?pvs=4
PRD: https://www.notion.so/cybnity/AC-2-8-Dynamic-account-management-72d42a96723c48e5b254c59fd24b6bc8?pvs=4 Approaches for dynamically creating, activating, managing, and deactivating system accounts rely on automatically provisioning the accounts at runtime for entities that were previously unknown. Organizations plan for the dynamic management, creation, activation, and deactivation of system accounts by establishing trust relationships, business rules (e.g security missions), and mechanisms with appropriate authorities (e.g security team owner; sub-division team) to validate related authorizations and privileges.
AC-2(8): Create, activate, manage, and deactivate [Assignment: organization-defined system accounts] dynamically. Family : ACCESS CONTROL
Used capabilities: Stakeholders and responsibilities UI Module server
USE CASES DESIGN
PROTOTYPING
CODING
TEST & NON REGRESSION CAMPAIGN
DOCUMENTATION
Component: Application System Security Control Implementation Component Implementation deployable system: Access control & sso server Technology layer: user interface area Technologies: nodeJS, keycloack, java, javascript, ReactJS