Main Menu » Security Settings

Security Settings


Set access restrictions and controls for MyConnection Server, the reporting account and database.

Access control list

You can limit access to all or part of the MyConnection Server to certain IP addresses.
The list below defines what is permitted. It is processed in-order, meaning that the first item to match is the one which is used. If no item in the list matches, the connection is automatically accepted.



Add new ACL item:
access
From (IP address or range, eg: 10.1.0.0-10.1.255.255)
To
URL: (* wildcard supported, eg: /myspeed/abc/*)

Automatic Log-on

Users can be automatically logged on based on their IP address. This allows you for example to specify an administrative IP address which is automatically granted administrative privileges. Note that clients can still log in as a different user if extra privileges are needed.
The following list defines those IP addresses which are automatically logged on.



Add new address:
IP address(es) (IP address or range, eg: 10.1.0.0-10.1.255.255)
User name

Cross-site Request Forgery Protection

Cross-site request forgery attacks can allow a user to unwittingly submit a form or click a URL which is hosted on a malicious site, but which targets MyConnection Server.
Enabling this option will require all future administrative access to be performed using forms submitted from the MyConnection Server itself.

Enable cross-site request forgery protection

Cookie set 'secure' when deploying MyConnection Server via a proxy

If MyConnection server is deployed behind a proxy (for example Apache) and the proxy serves it via https (the proxy does the encryption)
MyConnection Server is to add 'secure' option to the 'Set-Cookie' header.

Set 'secure' attribute to Set-Cookie

Cookie set 'httponly'

Enabling this option will restrict Java applets from obtaining the MCS session cookies from the browser. If enabled it is important to ensure that the MCS applet testing option is enabled for the 'public' user, otherwise testing in the browser will be permanently disabled.

Enable HTTPONLY cookies

Enable 'secure' mode for client XML iForward requests

iForward requests extend the MCS client side JavaScript API to allow any MCS client to forward a user defined data buffer to any external HTTP service. Enabling secure mode
enforces authentication testing for all iForward requests. iForward transactions that fail authentication are rejected by MCS and not forwarded to the HTTP service requested.

Set 'secure' attribute for iForward XML requests

Remote Agent Password

Before any Remote Agent can initiate a test to an MCS, NQC, Satellite Access server, the RA must first authenticate with the Server's Remote Agent password. By default or if blank, this is set to 'hello'.


NQC Client Password

Licensed NQC Apps for client platforms including iPhones, Android, Windows Phone are required to authenticate using the NQC client password. By default, this is set to 'hello'. Setting blank will deny all client Apps.


Database Post Password

Other MyConnection Servers will need this password in order to duplicate their results to this server. See the 'back-end server' option in the Database Configuration page.

Database Post Password

Password Specification

Enforce the following rules for all user account passwords:
Min number of characters
Min number of uppercase letters
Min number of lowercase letters
Min number of numeric digits
Min number of symbols (@#!...)
$PLUGINSCONFIGTEXT$