QPR Knowledge Base

Data Transfer Between Components

Hide Navigation Pane

Data Transfer Between Components

Previous topic Next topic No expanding text in this topic  

Data Transfer Between Components

Previous topic Next topic JavaScript is required for expanding text Mail us feedback on this topic!  

Comments (...)

Following image represents the data security issues in this chapter:

 

pic_data_transfer

Data Transfer between the Components

 

Every time that data moves from one place to another, there is always a risk that somebody is listening. This is especially a concern when data is being moved in the Internet.

 

To resolve this concern, QPR ScoreCard provides built-in security to some extent and allows many 3rd party security middlewares to take care of it.

 

 

Socket Connections

 

As illustrated in the image above, there are socket connections between the QPR ScoreCard Server and the Development Client as well as between the QPR ScoreCard Server and the QPR Web Application Server. Both of these connections are often made over an intranet and therefore are not a major concern. However, to provide superior data security, QPR ScoreCard has a built-in data encryption / authentication mechanism for these two connections, as intranet is not required for transferring data between clients and the server. Encryption mechanism is based on Microsoft Crypto Library. Note that using this encryption can cause problems if some of the clients are running on the Windows XP platform.

 

 

HTTP Connections

 

The QPR ScoreCard Web Client uses only the standard hypertext transfer protocol to transfer data to and from the Web Application Server. It is recommended to use a web server provided security layer like SSL in these connections. Also web server vendor-specific authentication methods can be used to provide even better security.

Comments (...)