Skip to main content

​
Overview

After the G360 server has been prepared, your organization must configure a secure way for users to access G360. This involves:
  • Creating a hostname
  • Configuring DNS
  • Enabling HTTPS using TLS
These requirements are typically managed by your organization’s infrastructure, network, or security team.

​
Configure a Hostname

G360 should be accessible through a hostname that is easy for your organization to identify. For example:
Users can access G360 through this hostname instead of connecting directly to the server’s IP address.

​
Configure DNS

Your organization’s DNS administrator must create a DNS record that points the G360 hostname to the appropriate infrastructure. Depending on your deployment, the hostname may point to:
  • The G360 server
  • A public or private IP address
  • A load balancer
The hostname is used to access both the G360 application and its API.

​
Application Paths

G360 uses the same hostname for different parts of the application. Common paths include:

​
Secure Access with HTTPS

G360 should be accessed using HTTPS. Your organization must configure a valid TLS/SSL certificate for the G360 hostname. HTTPS encrypts communication between users and the G360 application. For example:

​
TLS Configuration Options

TLS can be configured in one of the following ways:

​
TLS on the G360 Server

Your organization can configure the TLS certificate directly on the server hosting G360.

​
TLS Through a Load Balancer

If your organization uses a load balancer, the load balancer can manage HTTPS and forward traffic to G360.
When TLS is terminated by a load balancer, the deployment must correctly forward HTTPS information to G360.

​
Next Steps

After DNS and secure access have been configured, prepare the PostgreSQL database required by G360. Continue to Database Requirements.