Skip to main content

 

Eptura Knowledge Center

Security Center Configuration

The Proxyclick <> Security Center integration has the following prerequisites:

Networking

  • The Proxyclick access control client reaches out to Proxyclick servers via port 443. For more information on networking please refer to the 'Deployment Requirements' section of the [Access Control Overview](https://www.notion.so/f3868aa2319448...267972f?pvs=21) document.
  • The access control API listens on port 4590 by default, but depending on your setup this can change. Please confirm the correct port number with your access control administrator.
  •  The access control client needs to be able to reach the API.

Purchase the Genetec part code

To implement the Proxyclick integration the part code GSC-1SDK-Proxyclick-VM must be purchased from Genetec.  

Enable the Genetec WebSdk role

Ensure the WebSdk role is enabled in the Configuration tool. You can verify this by navigating to http://example.com:port/WebSdk
- replace example.com and port by the settings from your Genetec server.

 You should be prompted with a pop-up similar to the image below. Please keep in mind this needs to be accessible from the machine the Proxyclick Access Control Client will be installed on.
    
A manual firewall change may be necessary to be able to reach the Web SDK. Proxyclick supports SSL/TLS encrypted WebSDK connections if required, ensure the client machine accepts the certificate as a valid certificate via the browser to ensure the client will be able to accept the WebSDK certificate.

Set up the Proxyclick Card Format - for QR-based access

Set up the Proxyclick QR card format. **The format itself can be flexible** to easily align the wiegand formats with your reader. Requirements from Proxyclick are:

  •  At least 28 data bits
  •  The name to be (exactly including capitalisation): Proxyclick QR code
  •  A Wiegand field named (exactly including capitalisation): CardNumber

 

Refer to the Reading QR codes for more information.

Note on Parity

  • The above details worked well with AXIS controllers (A1601).
  • You may need to ignore any parity bits from the reader or ensure no parity is sent from the reader in order for this to work with Mercury controllers: they may not process the info correctly when parity is included in the reader output.

   

Set up a Proxyclick user

We recommend running the Proxyclick client under a specific Administrator. Go to 'User Administration' and add a new user for Proxyclick. Set this user as an administrator.

The password for this user will only be used by our client software and doesn’t need to be easily memorable. If your security policy with Genetec requires a different set of privileges, please contact your Access Control representative at Proxyclick.

Using Physical Credentials - RFID Cards/Fobs

Our Access Card Manager allows physical credentials to be assigned to a visitor via the Proxyclick dashboard. To configure this, we will need to know the Card Format and Facility Code configured for your RFID readers (only custom card formats supported). 

QR code setup steps (create and configure the Proxyclick Card Format) must be completed to enable the use of physical credentials.