Difference between revisions of "Loading into a remote CMOD server with SSL enabled"

Jump to navigation Jump to search
m
Minor corrections and improvements.
(Initial edit.)
 
m (Minor corrections and improvements.)
 
Line 1: Line 1:
{{TOCright}}
{{TOCright}}
= Background =
= Background =
In most CMOD servers, files are delivered to the CMOD server directly, and loaded using the [[arsload]] utility to ingest data locally.  This design is fairly secure - if files are delivered via an encrypted service (like SFTP) then unencrypted data doesn't traverse the network.  However, in some situations, it may make more sense of offload the 'heavy lifting' of the load process to a dedicated load server.  Without TLS/SSL enabled, then report data traverses the network in a compressed, but '''unencrypted''' format, which could be intercepted by an adversary with access to your network.   
In most CMOD servers, files are delivered to the CMOD server directly, and loaded using the [[arsload]] utility to ingest data locally.  This design is fairly secure - if files are delivered via an encrypted service (like SFTP) then unencrypted data doesn't traverse the network as part of the load process.  However, in some situations, it may make more sense to offload the 'heavy lifting' of the load process to a dedicated load server.  Without TLS/SSL enabled, then report data traverses the network in a compressed, but '''unencrypted''' format, which could be intercepted by an adversary with access to your network.   


To improve security of your Content Manager OnDemand system, you should absolutely be using TLS/SSL.
To improve security of your Content Manager OnDemand system, you should absolutely be using TLS/SSL when loading to Content Manager OnDemand remotely.


= Configuring ars.ini =
= Configuring ars.ini =

Navigation menu