 |
 |
 |
 |
 |
|
|
|
 |
 |
 |
|
 |
 |
 |
| | Security and Integration
|
| |
One of the first questions people ask when looking at integration technology is,
"What about security?" The obvious concern is for privacy and
authentication issues surrounding the connections between multiple data systems.
All of the integration approaches we have mentioned (ERP, EAI, EII, Portals and Veraterm)
must address the topic of security.
The integration security issues can be summarized as follows:
 |
 |
 |
Authorization and logins are handled differently by the systems being integrated.
Integration products must accommodate multiple systems and adapt to different approaches. |
 |
A single user may have different user names, passwords and authority levels in
different data systems. An integration product must manage and forward user
logins, so the user does not need to constantly log in, separately, to multiple data systems. |
 |
An integration product needs a trust relationship with the systems it integrates.
This means that the systems also need a way to authenticate the integration product,
itself.
|
How does the Veraterm System Handle Integration Security?
The Veraterm System utilizes an "assignment-based" security system, which is built to adapt to
the security systems of other database applications. For example, the Veraterm security system
is easily configured to mimic the role-based security model used by Microsoft SQL-Server.
The Veraterm security system manages system logins and connections. The user can be authenticated
by the Windows login, a separate unique login, or by the login of one of the systems being integrated.
In the case of unsecured databases, the Veraterm System can provide a security mechanism that is easier to
implement than some native security models. Such is the case with Microsoft Access databases
where its native security model is difficult for non-technical staff members to administer.
|
| |
Workflow Integration
|
|