The Hive Migrator service is responsible for migrating metadata and communication between agents.
Find details here for configuring the Hive Migrator service.
When basic authentication is enabled on Hive Migrator, update the LiveData UI with the credentials to maintain functionality.
Follow these steps to enable basic authentication on the Hive Migrator REST API:
In the security section, ensure enabled: is set to "true". For example,Ensure the enabled parameter is true
micronaut: security: enabled: true
Save and close the file.
Apply these steps if basic authentication is enabled on the LiveData Migrator REST API
In the LiveDataMigrator block, add
password. Both credentials should match those used for LiveData Migrator core.Example
integration: liveDataMigrator: port: 18080 useSsl: false username: "admin" password: "password"
passwordproperties to the integration section.
Don't indent: these are top-level properties. Use your LiveData Migrator username so you only need to authenticate once when connecting with 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.Example
integration:liveDataMigrator: port: 18080 useSsl: false username: "admin" password: "password"storagePath: /opt/wandisco/hivemigrator/hivemigrator.dbusername: "admin"password: "$2a$10$3gc/9QTnGQQj51e0YRAK.OAplbj4A9S4sx7rRpMSOSpb5UrLW2p/."
Restart the Hive Migrator service to enable the new configuration:
service hivemigrator restart
The username and password values can be changed without having to restart the Hive Migrator service. They will become active when you save the file.
Follow these steps if you used different credentials for LiveData Migrator and Hive Migrator, or if basic authentication isn't enabled on LiveData Migrator.
If you have used the same credentials for both services, this step isn't required.
When basic authentication is enabled, enter the username and password when prompted to connect to Hive Migrator with 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 Hive Migrator and the remote agent. These are placed in the following directories:
Generate new certificates for Hive Migrator and all remote agents that are connected.
Generating certificates for just one of these components breaks existing connections.
Generate new certificates and keys by using the following Hive Migrator REST API endpoints:
The remote agent service restarts automatically when you generate new certificates this way. You don't need to restart the Hive Migrator service to use the new certificates.
We support SSL for remote agents. SSL for remote agents is enabled by default. To use SSL for authentication and encryption, complete the following steps:
Enable SSL by manually setting the following parameter value:
sslEnabled = truein the configuration file
application.yamlfor Hive Migrator and for the Hive Migrator remote agent.
agentType: HIVEremoteAgentConfig:host: hostport: 5052sslEnabled: true
Generate self-signed certificates for Hive Migrator as the client and Hive Migrator remote agent as the server.
Use the following files names:
Copy the following files to the Hive Migrator directory
Copy the following files to the Hive Migrator remote server directory
Restart the service for the Hive Migrator remote server by running the command:
service hivemigrator-remote-server restart
Make sure the correct certificates and keys are uploaded for Hive Migrator and all remote agents that are connected.
Existing connections will break if the trust relationship isn't established between Hive Migrator and remote agents.
Upload certificates and keys by using the following Hive Migrator REST API endpoints:
The remote agent service restarts automatically when new certificates are uploaded this way. The Hive Migrator service doesn't require a restart to start using new certificates.
The following directories are used for Hive Migrator:
|Java archive files|
The following directories are used for Hive Migrator remote servers (remote agents):
|Java archive files|