dhtmlxConnector is open to external access of another programs and any external user is allowed to change data in database.
Thus, adding some kind of session-based authentication is strongly recommended.
The built-in security manager allows limiting connector to certain operations.
grid.access.deny(OperationType.Read); //blocks Select action grid.access.deny(OperationType.Insert); //blocks Insert action grid.access.deny(OperationType.Update); //blocks Update action grid.access.deny(OperationType.Delete); //blocks Delete action
By default, connector allows all operations.
Starting from version 1.5, dhtmlxConnector allows you to protect an app from XSS attacks.
3 security levels are available:
To set the necessary security level, use the next code:
ConnectorSecurity.xss = ConnectorXSSMode.DHX_SECURITY_TRUSTED //ConnectorSecurity.xss = ConnectorXSSMode.DHX_SECURITY_SAFEHTML //ConnectorSecurity.xss = ConnectorXSSMode.DHX_SECURITY_SAFETEXT
If you want to enable the same behavior as the previous versions of connectors had, set the DHX_SECURITY_TRUSTED mode.
The functionality requires 3.5 or later version of the DHTMLX Suite package
The protection is available starting from version 1.5 and can be activated by the following code line:
ConnectorSecurity.security_key = true;
After calling such a command, connectors start to include additional security keys to all data loading operations and process data updating calls only if they contain the same keys. As a result of this processing, it's impossible to trigger a data updating operation from some third-party site, even if an attacker has access to the valid user session.
Please be sure that you understand what CSRF attack is, cause the stated technique won't prevent access to the connector from external urls, it will only prevent execution actions through someone else's session.Back to top