WoodWing Help Center

Defining remote and local users in Enterprise Server 9

Defining remote and local users in Enterprise Server 9

Users who work on remote locations and who are connected to Enterprise Server through a slow connection can suffer from poor performance such as long waiting times when saving files.

To improve the performance, a distinction can be made in Enterprise Server between 'local' and 'remote' users and subsequently used by features such as compressing articles for remote Content Station users, or offloading heavy InDesign tasks such as file generation for local users.

Configuring Enterprise Server

Info: This feature requires Enterprise Server version 9.5.0 or higher.

Whether a user is considered to be local or remote is controlled by defining the user's IP address — or a range of IP addresses — in the configserver.php file of Enterprise Server through an 'include' and 'exclude' option.

It works as follows:

  • Remote users are all users who are defined in the 'include' option.
  • Local users are all users who are defined in the 'exclude' option.

Note:

  • The check to see in which group a user falls is done when the user logs in.
  • The 'exclude' option overrules the 'include' option, meaning that when a user falls under an IP address that is defined under both options, the 'exclude' option 'wins' and the user is seen as a local user.
  • When both options are left empty (which is the default configuration), all users are treated as local users.

Step 1. In the configserver.php file of Enterprise Server, locate the Remote users section.

// ---------------------------------------------------------------------- 
// Remote users 
// ---------------------------------------------------------------------- 

Step 2. Define the IP addresses of the users who should be treated as a remote user under the INCLUDE option (for details about defining these addresses see below):

define( 'REMOTE_LOCATIONS_INCLUDE', serialize( array(
)));

Step 3. Define the IP addresses of the users who should be treated as a local user under the EXCLUDE option (for details about defining these addresses see below):

define( 'REMOTE_LOCATIONS_EXCLUDE', serialize( array(
))); 

Defining IP addresses

Use any of the following notations:

IP range Matches with
'192.0.0.1' '192.0.0.1' only
'192.0.0.*' ['192.0.0.0'...'192.0.0.255']
'192.0.*.*' ['192.0.0.0'...'192.0.255.255']
'192.0.0.0/16' ['192.0.0.0'...'192.0.255.255']
'192.0.0.0/24' ['192.0.0.0'...'192.0.0.255']
'192.0.0.0/255.255.0.0' ['192.0.0.0'...'192.0.255.255']
'192.0.0.0/255.255.255.0' ['192.0.0.0'...'192.0.0.255']
'192.0.0.0-192.0.0.255' ['192.0.0.0'...'192.0.0.255']
'192.0.0.0-192.0.255.255' ['192.0.0.0'...'192.0.255.255']
'2001:db8::1' '2001:db8:0:0:0:0:0:1' only
'2001:db8::/32' ['2001:db8:0:0:0:0:0:0'...'2001:db8:ffff:ffff:ffff:ffff:ffff:ffff']
'2001:db8::/64' ['2001:db8:0:0:0:0:0:0'...'2001:db8:0:0:ffff:ffff:ffff:ffff']
'2001:db8::-2001:db9::' ['2001:db8:0:0:0:0:0:0'...'2001:db9:0:0:0:0:0:0']
'2001:db8::-2001:db8::ff' ['2001:db8:0:0:0:0:0:0'...'2001:db8:0:0:0:0:0:ff']

Examples:

define( 'REMOTE_LOCATIONS_INCLUDE', serialize( array(
'192.0.0.1'
)));

define( 'REMOTE_LOCATIONS_INCLUDE', serialize( array(
'192.268.0.1',
'2001:db8::/64'
)));
Was this article helpful?
0 out of 0 found this helpful / Created: / Updated:
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.