Download the PHP package aerticket/data-anonymizer without Composer
On this page you can find all versions of the php package aerticket/data-anonymizer. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download aerticket/data-anonymizer
More information about aerticket/data-anonymizer
Files in aerticket/data-anonymizer
Package data-anonymizer
Short Description Anonymize sensitive data in your models via annotations
License MIT
Homepage https://github.com/aerticket/neos-flow-data-anonymizer
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package data-anonymizer
Data Anonymizer for Neos Flow Applications
Anonymize sensitive data in your models via annotations
Installation
Install the package via composer:
(or by adding the dependency to the composer manifest of an installed package)
Basic usage
You can define which models should be anonymized via annotations:
The referenceDate option of the class annotation is mandatory. It is the path to the property that contains the date that
is used to determine the age of the entity. You can use the same syntax as a query condition (e.g.
relatedObject.anotherRelatedObject.creationDate).
To actually trigger the anonymization process, you have to call the following flow command:
Please note that a maximum number of 100 entities is anonymized per class and run. If more entities have to be anonymized, you have to run the command several times.
Anonymize given entities
If you need to manually trigger data anonymization (e.g. user data that can be cleared after having been processed), you can explicitly anonymize a given entity:
You can work on not (yet) persisted objects as well by avoiding an update of the record in its repository with the second parameter to anonymizeEntity.
Configuration options
Age
You can define the age after which entities should be anonymized. The default value is configured via Settings.yaml:
If you want to override this value for a specific class, you can use the anonymizeAfter option of the AnonymizableEntity
annotation.
Anonymized values
When anonymizing an entity, a anonymized value is set for each property that should be anonymized. For different property types (string, integer), different default values are configured via Settings.yaml.
If you want to use an individual value for a specific property, you can add the value to the Anonymize annotation
of the property:
Limitations
The following limitations apply at the moment:
- This package only works with entities that have its own repository.
- Anonymization of nested properties is non implemented yet.
