The HiveMigrator service is responsible for communication between agents and migration of metadata.
Find details here for configuring the HiveMigrator service.
When basic authentication is enabled on HiveMigrator, update the LiveData UI with the credentials to maintain functionality.
Follow these steps to enable basic authentication on the HiveMigrator REST API:
/etc/wandisco/hivemigrator/application.yamlfile to enable authentication:Change the enabled parameter from false to true
micronaut: security: enabled: true
If basic authentication is enabled on the LiveData Migrator REST API, add two properties,
password, inside the integration section of the
/etc/wandisco/hivemigrator/application.yamlfile. Use the same username for HiveMigrator and LiveData Migrator. If the LiveData Migrator credentials and the HiveMigrator credentials (defined in the next step) are the same, you will only need to authenticate once when connecting through the CLI.
The password string needs to be encrypted using a bcrypt generator that provides a "2a" prefix at the beginning of the encrypted password, as shown in the following example.Example
micronaut:liveDataMigrator: port: 18080 useSsl: false username: "admin" password: "password"storagePath: /opt/wandisco/hivemigrator/hivemigrator.dbusername: "admin"password: "$2a$10$3gc/9QTnGQQj51e0YRAK.OAplbj4A9S4sx7rRpMSOSpb5UrLW2p/."
Restart the HiveMigrator service to enable the new configuration:
service hivemigrator restart
The username and password values can be changed without having to restart the HiveMigrator service. They will become active once you have saved the file.
Follow these steps if you have used different credentials for LiveData Migrator and HiveMigrator, or if basic authentication is not enabled on LiveData Migrator.
If you have used the same credentials for both services, this step is not required.
When basic authentication is enabled, provide the username and password when prompted to connect to HiveMigrator through the CLI:
connect hivemigrator localhost: trying to connect...Username: adminPassword: ***********Connected to hivemigrator v1.2.1-428 on http://localhost:6780.
The username and password will also be required when accessing the HiveMigrator REST API directly.
Certificates (and keys) are automatically generated for this connection for both HiveMigrator and the remote agent. These are placed in the following directories:
You must generate new certificates for HiveMigrator and all remote agents that are connected.
Generating certificates for just one of these components will break existing connections.
Generate new certificates and keys by using the following HiveMigrator REST API endpoints:
The remote agent service will automatically restart when new certificates are generated this way. The HiveMigrator service does not require a restart to start using new certificates.
Make sure the correct certificates and keys are uploaded for HiveMigrator and all remote agents that are connected.
Existing connections will break if the trust relationship is not established between HiveMigrator and remote agents.
Upload certificates and keys by using the following HiveMigrator REST API endpoints:
The remote agent service will automatically restart when new certificates are uploaded this way. The HiveMigrator service does not require a restart to start using new certificates.
The following directories are used for HiveMigrator:
|Java archive files|
The following directories are used for HiveMigrator remote servers (remote agents):
|Java archive files|