Enabling HTTP(S) and FTP(ES)

Solution Installation > Netrix Installation > Configure TSS / TPO

Booting Netrix

When Netrix boots it tries to connect to the TSS Server defined by DHCP Option 171 (or the override set via the Network Tab)


		Netrix no longer requires the FTP Server during its boot up.

Booting using HTTP

If the DHCP Option (or TSS address override on the Network Tab) is an IP address, Netrix will attempt to boot from the TSS using the HTTP protocol.

In the TSS Component Manger make sure Prevent HTTP usage is set to disabled;

Netrix-EnableHttp

Booting using HTTPS

If the TSS address override on the Network Tab is a FQDN, Netrix will attempt to connect to the server using the HTTPS protocol.

The TSS will require

•a CA Certificate to be installed

•HTTPS to be enabled on the TSS Component Manager.

If the turret

•is configured to use HTTPS but is unable to establish the connection it will not downgrade to using insecure HTTP.

•is unable to validate the server, it will ask the user whether they trust the server. If the answer is yes, the turret will update its persisted bundle of certificates and continue to connect to the server. If the answer is no, the turret will reboot.

Booting with HTTP Authentication

If the TSS has been configured to require turrets to use Basic HTTP Authentication when they boot up, then authentication details should be entered on the TSS Tab.

Connecting to the TSS

Once Netrix has booted up it will connect to the TSS defined by the boot settings application.bscg.baseServiceURI and application.bscg.alternateServiceURI

Important_icon

Netrix supports HTTPS to the TSS.

If you wish to continue using HTTP between Netrix and TSS, you will need to override aplication.bscg.baseServiceURI and application.bscg.alternateServiceURI for the Netrix zone(s) to specify HTTP protocol.

Connecting using HTTP

If the URIs specify an HTTP scheme, Netrix will try and connect using HTTP protocol.

In the TSS Component Manger make sure Prevent HTTP usage is set to disabled.