Browse documentation for IT-systems used by the European Environment Agency and the Eionet network.
This repository contains two scripts which obfuscate data from bdr registry database and generate a ldif file for LDAP account changes.
The repository contains a script which obfuscates persons and companies data from BDR-registry database.
Clone this project:
$ git clone https://github.com/eea/bdr.registry.dataobfuscation.git $ cd bdr.registry.dataobfuscation
Set the target BDR-registry database name, the MySQL root password and a default password for all company accounts:
$ cp mysql.env.example mysql.env $ vi mysql.env $ source mysql.env
The obfuscation script expects to find the source database file in the same folder under the name dump.sql. The target database should exists in a local MySQL server.
WARNING: The existing target database will be overwritten!
After the BDR-registry data obfuscation, ldap database must be updated with the new accounts. This script will generate a ldif file named bdr.ldif, in the current directory, ready for import.
Calling the script without any arguments will generate a full dummy data ldif,
for the eionet branch and the Business Reporters branch. In order to properly
populate the eionet branch with users, it expects the eionet.users file to be
user:password entries, one entry for each line.
There are 3 named arguments required by the script:
--type=full|eionet|bdr --rootuid=<uid_of_the_root_user> --rootpw=<password_for_the_root_user>
The type indicates which branch to be populated, full means that both eionet and the business reporter branches are going to be populated, while bdr will only generate the initial structure of the eionet branch with the additional root user defined. eionet will only generate the eionet branch. rootuid and rootpw are used to generate an entry to be used as the root dn. A typical call would then look like:
$ ./ldap.sh --type=full --rootuid=foo --rootpw=bar
The template for the ldif is defined in the ldap_template.txt template file.