The installation without balancing includes installation of the management server and access servers (SSH-Proxy or RDP-Proxy) on different servers. |
Before you begin the installation, prepare the configuration files. |
Edit the inventory file:
# NOTE: To access docker host use local.docker name instead of localhost [management] pammng.test.local [access] pamgtw.test.local remote_ssh_user=root ansible_ssh_password=123 ansible_become_password=123 #[haproxy] #HAPROXY_SERVER_FQDN_OR_IP #[rds] #RDS_SERVER_FQDN_OR_IP # Use this section to override vars #[all:vars] #server_fqdn=OVERRIDE_SERVER_FQDN |
Unzip the downloaded configuration files and move the extracted folders to indeed-pam-linux\state.
Move the CA certificate along the path indeed-pam-linux\state\ca-certificates.
|
Go to indeed-pam-linux\state\certs and create a separate folder for the management server. Name it with the FQDN name of the management server.
|
Move the management server certificate to the folder corresponding to the management server.
|
Go to indeed-pam-linux\state\keys\rdp-proxy and create a separate folder for the access server. Name it with the FQDN name of the access server.
|
Move the access server certificate to the folder corresponding to the access server.
|
If CIS Benchmark Docker security settings are applied, then run the installation script with the command:
sudo bash run-deploy.sh |
If CIS Benchmark Docker security settings are not applied, then run the installation script with the command:
sudo bash run-deploy.sh -bench-skip |
If the script aborted with an error, send the log file to technical support. |
Restarting all of the components:
sudo docker compose -f docker-compose.management-server.yml down sudo docker compose -f docker-compose.management-server.yml up -d or sudo docker-compose -f docker-compose.management-server.yml down sudo docker-compose -f docker-compose.management-server.yml up -d |
Restarting a specific component:
sudo docker compose -f docker-compose.management-server.yml up -d <component name> --force-recreate or sudo docker-compose -f docker-compose.management-server.yml up -d <component name> --force-recreate |
Example of restarting the Axidian Privilege Core component:
sudo docker compose -f docker-compose.management-server.yml up -d core --force-recreate or sudo docker-compose -f docker-compose.management-server.yml up -d core --force-recreate |
Restart Axidian Privilege access server components using the following commands:
sudo docker compose -f docker-compose.access-server.yml down sudo docker compose -f docker-compose.access-server.yml up -d or sudo docker-compose -f docker-compose.access-server.yml down sudo docker-compose -f docker-compose.access-server.yml up -d |