matiux/broadway-sensitive-serializer-bundle
Composer 安装命令:
composer require matiux/broadway-sensitive-serializer-bundle
包简介
Bundle for serializer implementation with support for data sensitization
关键字:
README 文档
README
This bundle is the wrapper for the Broadway Sensitive Serializer library. You can find more info on the base library here.
Setup for development
git clone https://github.com/matiux/broadway-sensitive-serializer-bundle.git && cd broadway-sensitive-serializer-bundle cp docker/docker-compose.override.dist.yml docker/docker-compose.override.yml rm -rf .git/hooks && ln -s ../scripts/git-hooks .git/hooks
Install dependencies to run test or execute examples
make build-php ARG="--no-cache" make upd make composer ARG="install"
Run test
make build-php ARG="--no-cache"
make upd
make phpunit
Whole Strategy configuration
broadway_sensitive_serializer: aggregate_master_key: 'm4$t3rS3kr3tk31' # Master key to encrypt the keys of aggregates. Get it from an external service or environment variable key_generator: open-ssl # For now is the only one generator implemented # To use the DBAL implementation, install matiux/broadway-sensitive-serializer-dbal package with composer aggregate_keys: broadway_sensitive_serializer.aggregate_keys.dbal #aggregate_keys: broadway_sensitive_serializer.aggregate_keys.in_memory # Default implementation, of little use outside of testing data_manager: name: AES256 # For now, it is the only encryption strategy implemented key: null # Encryption key to sensitize data. If null you will need to pass the key at runtime. This is the convenient way, check out the examples and wiki on main library iv: null # Initialization vector. If null it will be generated internally and iv_encoding must be set to true. This is the convenient way, check out the examples and wiki on main library iv_encoding: true # Encrypt the iv and is appends to encrypted value. It makes sense to set it to true if the iv option is set to null. This is the convenient way, check out the examples and wiki on main library #--- Alternatively ----- #data_manager: # name: AES256 # parameters: # AES256: # key: null # iv: null # iv_encoding: true strategy: name: whole aggregate_key_auto_creation: true # Enable AggregateKey model auto creation. This is the convenient way, check out the examples and wiki on main library value_serializer: json # Strategy to serialize payload's values. Default json excluded_id_key: id # The key of the aggregate id which should not be encrypted excluded_keys: # List of keys to be excluded from encryption - occurred_at events: # List of events supported by the strategy - SensitiveUser\User\Domain\Event\AddressAdded - SensitiveUser\User\Domain\Event\UserRegistered #--- Alternatively ----- #strategy: # name: whole # parameters: # whole: # aggregate_key_auto_creation: true # value_serializer: json # excluded_id_key: id # excluded_keys: # - occurred_at # events: # - SensitiveUser\User\Domain\Event\AddressAdded # - SensitiveUser\User\Domain\Event\UserRegistered
Partial Strategy configuration
broadway_sensitive_serializer: aggregate_master_key: 'm4$t3rS3kr3tk31' # Master key to encrypt the keys of aggregates. Get it from an external service or environment variable key_generator: open-ssl # For now is the only one generator implemented # To use the DBAL implementation, install matiux/broadway-sensitive-serializer-dbal package with composer aggregate_keys: broadway_sensitive_serializer.aggregate_keys.dbal #aggregate_keys: broadway_sensitive_serializer.aggregate_keys.in_memory # Default implementation, of little use outside of testing data_manager: name: AES256 # For now, it is the only encryption strategy implemented key: null # Encryption key to sensitize data. If null you will need to pass the key at runtime. This is the convenient way, check out the examples and wiki on main library iv: null # Initialization vector. If null it will be generated internally and iv_encoding must be set to true. This is the convenient way, check out the examples and wiki on main library iv_encoding: true # Encrypt the iv and is appends to encrypted value. It makes sense to set it to true if the iv option is set to null. This is the convenient way, check out the examples and wiki on main library #--- Alternatively ----- #data_manager: # name: AES256 # parameters: # AES256: # key: null # iv: null # iv_encoding: true strategy: name: partial aggregate_key_auto_creation: true # Enable AggregateKey model auto creation. This is the convenient way, check out the examples and wiki on main library value_serializer: json # Strategy to serialize payload's values. Default json events: # List of events supported by the strategy - SensitiveUser\User\Domain\Event\AddressAdded: - address # List of keys to sensitize - SensitiveUser\User\Domain\Event\UserRegistered: - name - surname #--- Alternatively ----- #strategy: # name: partial # parameters: # partial: # aggregate_key_auto_creation: true # value_serializer: json # events: # - SensitiveUser\User\Domain\Event\AddressAdded: # - address # - SensitiveUser\User\Domain\Event\UserRegistered: # - name # - surname
Custom Strategy configuration
broadway_sensitive_serializer: aggregate_master_key: 'm4$t3rS3kr3tk31' # Master key to encrypt the keys of aggregates. Get it from an external service or environment variable key_generator: open-ssl # For now is the only one generator implemented # To use the DBAL implementation, install matiux/broadway-sensitive-serializer-dbal package with composer aggregate_keys: broadway_sensitive_serializer.aggregate_keys.dbal #aggregate_keys: broadway_sensitive_serializer.aggregate_keys.in_memory # Default implementation, of little use outside of testing data_manager: name: AES256 # For now, it is the only encryption strategy implemented key: null # Encryption key to sensitize data. If null you will need to pass the key at runtime. This is the convenient way, check out the examples and wiki on main library iv: null # Initialization vector. If null it will be generated internally and iv_encoding must be set to true. This is the convenient way, check out the examples and wiki on main library iv_encoding: true # Encrypt the iv and is appends to encrypted value. It makes sense to set it to true if the iv option is set to null. This is the convenient way, check out the examples and wiki on main library #--- Alternatively ----- #data_manager: # name: AES256 # parameters: # AES256: # key: null # iv: null # iv_encoding: true strategy: name: custom aggregate_key_auto_creation: true # Enable AggregateKey model auto creation. This is the convenient way, check out the examples and wiki on main library value_serializer: json # Strategy to serialize payload's values. Default json #--- Alternatively ----- #strategy: # name: custom # parameters: # custom: # aggregate_key_auto_creation: true # value_serializer: json
matiux/broadway-sensitive-serializer-bundle 适用场景与选型建议
matiux/broadway-sensitive-serializer-bundle 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 130 次下载、GitHub Stars 达 0, 最近一次更新时间为 2022 年 01 月 07 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「symfony」 「bundle」 「serializer」 「ddd」 「cqrs」 「domain-driven design」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 matiux/broadway-sensitive-serializer-bundle 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 matiux/broadway-sensitive-serializer-bundle 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 matiux/broadway-sensitive-serializer-bundle 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
Bridge between JMS Serializer Bundle and Superdesk Web Publisher.
2lenet/EasyAdminPlusBundle
De/normalize business objects without tightly coupling them to your normalization format
The bundle for easy using json-rpc api on your project
Provide a way to secure accesses to all routes of an symfony application.
DMS Meetup API Bundle, enables Meetup API clients in services
统计信息
- 总下载量: 130
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 0
- 点击次数: 6
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2022-01-07