...
Create a blank database on the server. An already existing database can be used, but this is not recommended.
Add a user that will be used as the owner of the related tables but also to authenticate with the server.
In order to install or perform upgrades, this database user will require DDL (Data Definition Language) permission in the database during the installation or the upgrade.
Once the install or upgrade has been completed successfully, the configured database user requires only DML (Data Manipulation Language) permissions.
Here is how to configure the database for a local installation where the database server is on the same host. For multi-node installation please refer to your database administrator.
Note: The following steps require Administrator privilege, be sure that you have the correct access before continuing.
Install a PostgreSQL database server.
Once the installation is complete, initialize the PostgreSQL database.
Start the PostgreSQL Server:
For eaxmple, from the Service Management Console management:
Create a user for UDMG Waarp Gateway
Login as PostgreSQL user, start the PostgreSQL Console (psql) and create the database user:
Code Block |
---|
postgres=# create database mft_waarp_gateway; CREATE DATABASE postgres=# create user mft_waarp_gateway_user with encrypted password 'mft_waarp_gateway_password'; CREATE ROLE postgres=# grant all privileges on database mft_waarp_gateway to mft_waarp_gateway_user; GRANT |
Finally change the pg_hba.conf, to allow database connection with password. For example, for a system where the database server is on the same host as the UDMG server, by changing this line from:
Code Block |
---|
host all all 127.0.0.1/32 ident |
to:
Code Block |
---|
host all all 127.0.0.1/32 md5 |
The exact configuration depends on the OS and database version, on the preferred security settings, and on the system architecture.
The location of the pg_hba.conf can be returned by PostgreSQL Console (psql):
|
NGINX Server
Note: The following steps require root privilege, be sure that you have the correct access before to continue.
Install a NGINX Server (nginx for Windows).
Run the following command to check the main NGINX configuration file:
C:\MFT\nginx-1.23.0> nginx -t
nginx: the configuration file C:\MFT\nginx-1.23.0/conf/nginx.conf syntax is ok
nginx: configuration file C:\MFT\nginx-1.23.0/conf/nginx.conf test is successfully
Create a directory under the configuration folder called "enabled" and add an include directive in the main configuration file inside the http section. For example
http {
include mime.types;
default_type application/octet-stream;
include "C:/MFT/nginx-1.23.0/conf/enabled/*.conf"
...
C:\>curl.exe http://localhost:8080
<html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
<hr><center>nginx/1.23.0</center>
</body>
</html>
This error (403) is excepted, since we don't have any asset deployed.
Note: for configuring HTTPS and HTTP redirection, please refer to the web server documentation.
UDMG Admin UI
Uncompress the tar file for MFT Admin UI, under the directory that we created during the configuration.
...
C:\>curl.exe http://localhost:8080 -I
HTTP/1.1 200 OK
Server: nginx/1.23.0
Date: Thu, 07 Jul 2022 17:53:09 GMT
Content-Type: text/html
Content-Length: 7788
Last-Modified: Fri, 01 Jul 2022 13:58:15 GMT
Connection: keep-alive
ETag: "62befd77-1e6c"
Accept-Ranges: bytes
or with the browser:
UDMG Server
Create the configuration file C:\MFT\MFT Gateway\server.ini with the following parameters:
...
Configuration for LDAP Authentication
The UDMG Authentication Proxy is capable to use a LDAP Service to authenticate users for UDMG Admin UI:
# Proxy Configuration
[proxy]
# Enable Auto Recover
recover = true
# Enable Cors
cors = true
# Enable Request Track ID
tracker = false
# Enable Logguer
logger = true
# Listen Port
port = "5000"
# Listen IP
inet = "127.0.0.1"
# Service with LDAP Authentication
[service.mft]
# MFT Waarp Gateway Listen Protocol
protocol = "http"
# MFT Waarp Gateway Hostname or IP
hostname = "localhost"
# MFT Waarp Gateway Port
port = "18080"
# This option is breaking glass option for admins, they will not reach the LDAP service during the Auth Stage
admins = ["admin"]
# User for Sync Password Between Ldap and Proxy
[service.mft.credential]
# Pre - Setup user under MFT Waarp Gateway
username = "ldap_sync"
password = "ldap_password"
# LDAP Configuration
[service.mft.auth.ldap]
# LDAP Server DC with OU
dn = "ou=users,dc=stonebranch,dc=com"
# LDAP Server FQDN or IP
hostname = "myldap.server.fqdn.com"
# LDAP Server pORT
port = "1389"
The LDAP replication requires a user with permission for creating and updating users. For example to create the 'ldap_sync' user with the command line interface: waarp_gateway user add -u ldap_sync -p ldap_password -r 'U=rw' |
UDMG Agent Proxy
Create a directory C:\MFT\MFT Agent
Install the binaries as mft_agent_proxy_client and mft_agent_proxy_server
...
# ssh-keygen -t rsa -q -N "" -f /etc/mft/agent_proxy/agent
# ssh-keygen -t rsa -q -N "" -f /etc/mft/agent_proxy/client
If OpenSSH is not installed or not available, the PuTTY tool can be used instead.
Use PuTTYgen to generate a key pair for the agent, more detailled instructions can be found here: https://the.earth.li/~sgtatham/putty/0.77/htmldoc/Chapter8.html#pubkey-puttygen
After generating the key, export it with OpenSSH format:
Create a configuration file as C:\MFT\MFT Agent\agent\agent.toml
[agent]
# Listen IP Address
hostname = "0.0.0.0"
# Listen Port
port = "2222"
# SSH Priv Key
ssh_key = "agent"
# SSH Public Key
ssh_key_pub = "agent.pub"
# Service User
username = "mft"
# Service Password
password = "61ee8b5601a84d5154387578466c8998848ba089"
The password key will be used for the client authentication.
Client Configuration
Create a configuration file as C:\MFT\MFT Agent\client\client.toml
[client]
# MFT Agent Proxy Hostname or IP
hostname = "localhost"
# MFT Agent Proxy Listen Port
port = "2222"
# SSH Priv Key
ssh_key = "/etc/mft/agent_proxy/client"
# SSH Public Key
ssh_key_pub = "/etc/mft/agent_proxy/client.pub"
# Service User
username = "mft"
# Service Password
password = "61ee8b5601a84d5154387578466c8998848ba089"
# Default TTL to Connection Retry
ttl="5s"
# MFT Agent Client Admin API
[client.api]
# Listen Port
port="2280"
# MFT Waarp Gateway
[gateway]
# MFT Waarp Gateway Hostname or IP
hostname = "localhost"
# MFT Waarp Gateway Port
port = "18080"
# MFT Waarp Gateway Username/Password
username = "admin"
password = "admin_password"
The password key will be used for the client authentication.
Setup the Windows Services
UDMG Server
Open a PowerShell console and create a new service definition:
$params = @{
Name = "MFT Waarp Gateway Server"
BinaryPathName = '"C:\MFT\MFT Gateway\waarp-gatewayd.exe" server -c "C:\MFT\MFT Gateway\server.ini"'
DisplayName = "MFT Waarp Gateway Server"
StartupType = "Automatic"
Description = "MFT Waarp Gateway Server."
}
New-Service @params
...
Start-Service "MFT Waarp Gateway Server"
Be sure that the listen port and network interface is reachable by UDMG Authentication Proxy and UDMG Agent Client.
UDMG Authentication Proxy
...
Start-Service "MFT Auth Proxy server"
Be sure that the listen port and network interface is reachable by NGINX Server.
UDMG Agent Proxy
Agent Proxy Server Service
...
Start-Service "MFT Agent Server"
Be sure that the listen port and network interface is reachable by UDMG Agent Client .
Agent Proxy Client Service
...
Start-Service "MFT Agent Client"
Component Ports
Make sure that all the ports needed are open under your firewall configuration.
References
This document references the following documents.
Name | Location |
---|---|
PostgreSQL Client Authentication | https://www.postgresql.org/docs/current/auth-pg-hba-conf.html |
PostgreSQL Password Authentication |