Architecture
Here is the architecture for Proxyclick's access control integration:
.png?table=block&id=32d57af7-2650-44c0-8e13-4fa58148d4bf&spaceId=13c6e454-12a5-4f3b-a8c7-71910d91f388&width=2000&userId=&cache=v2)
The image below shows the layout of a typical access control integration using the Proxyclick client software:
.png?table=block&id=8f89f5b2-48f5-445b-81eb-0c0a4d372ca7&spaceId=13c6e454-12a5-4f3b-a8c7-71910d91f388&width=1950&userId=&cache=v2)
The client software acts as a secure conduit between the Proxyclick servers in the cloud and the access control server under the client's domain, typically on-site.
The client software can be deployed on the same machine that the access control system (ACS) runs on or on a separate server (if the ACS supports remote connections).
Please note that no client software will be required if using a cloud-based access control system. A direct connection from Proxyclick to the cloud-based ACS will be made.