Difference between revisions of "OS4X Portal"

From OS4X
Jump to navigation Jump to search
Line 8: Line 8:
 
= Components =
 
= Components =
 
OS4X Portal consists of several components being used:
 
OS4X Portal consists of several components being used:
 +
 +
*[[OS4X Portal - licensing|Special portal license]]
  
 
== Internal ==
 
== Internal ==
*[[OS4X Portal - licensing|Special portal license]]
 
 
*Portal definition
 
*Portal definition
 
*User management and synchronization
 
*User management and synchronization
Line 19: Line 20:
  
 
== External ==
 
== External ==
*Special portal license
 
 
*OS4X client daemon
 
*OS4X client daemon
 
*Portal configuration
 
*Portal configuration

Revision as of 11:44, 8 April 2019

Product purpose

OS4X Portal is a portal solution for transferring files between an internal and external server for a secure data exchange with external communication partners, who typically don't have an own solution for managed data transfers.

Definition

  • OS4X Portal server: a server in the DMZ
  • OS4X Portal daemon: software handling portal jobs, running in the internal network zone

Components

OS4X Portal consists of several components being used:

Internal

  • Portal definition
  • User management and synchronization
  • OS4X Portal daemon
  • Portal send plugin
  • Portal receive plugin
  • shared storage

External

  • OS4X client daemon
  • Portal configuration
  • shared storage

Required communication ports

For a functional OS4X Portal communication, the following communication protocols needs to be enabled between internal to external zone:

  • shared storage, like:
    • NFS3 with ports 111 (TCP and UDP) and 2049 (TCP and UDP)
    • NFS4 with port 2049 (TCP)
    • CIFS with UDP ports 137 and 138, and TCP ports 139 and 445
  • http(s) communication via a defined port (TCP ports 80 or 443 by default)