Skip to main content

 

Eptura Knowledge Center

C•CURE 9000 Configuration

The Proxyclick <> C•CURE 9000 integration has the following prerequisites:

License Option - C-Cure v2.8 or later

  1. From v2.8 onwards, the Proxyclick to C-Cure integration requires an additional license option from Software House. Please purchase the "Proxyclick - CCURE 9000 Visitor Management" license option.
  2. For compatibility with v2.8+, you will need to run the below cmdlet on the machine running C-Cure 9000:

    "C:\Program Files (x86)\Tyco\CrossFire\Tools\InsertLicenseOption.exe" /U /V /S:".\SQLEXPRESS" /N:"Proxyclick - CCURE 9000 Visitor Management - Integration" /A:"Proxyclick" /G:66af3e32-5e45-4651-b2a5-96dd1c205f8e /C:2 /P:0

    The /S: parameter must point to your C-Cure SQL server: /S:".\SQLEXPRESS" may need to be altered to /S:".\MSSQL" for example. This should be the server address of the SQL Server - what you would use to connect via SQL Server Management Studio.

    Note: We have seen examples where the .\ needed to be removed from the server name. /S:".\SERVERNAME" failed and /S:"SERVERNAME" was successful.
     
  3. CCure services must be restarted once the above steps have been performed
  4. You should verify that the "Proxyclick - CCURE 9000 Visitor Management" license option displays as active in the CCure license manager (or via Help/About) before expecting the connection to function - this may not happen until the services have been restarted

Contact Tyco/Software House if unsure about this step or if any issues are encountered. They offer no support for the Proxyclick integration, so you may need to explain the issue relates specifically to running their cmdlet. This step is required before moving on to the steps below.

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 document.
  • The access control API listens on port 80 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.

Partitioning/MAS-SAS

Proxyclick’s integration has support for C•CURE 9000 instances in a MAS/SAS setup or a partitioned setup.

MAS/SAS The integration can connect to the Victor Webservice on either the MAS or the SAS depending on which partitions will need to be accessed and/or network limitations.

Partition The integration can be configured to create personnel (users), clearances (access levels) and credentials (tokens) in a specific partition. The Partition ID will need to be provided during installation.

Victor Web Service

http://example.com/victorwebservice/

If this URL isn’t accessible and you’ve followed all steps within the C•CURE 9000 documentation, contact C•CURE 9000 tech support for assistance. The website should look similar to this:

https://lh4.googleusercontent.com/A4lHgq-gyjn2M-kABXy8ket251-tn1avumyisZ9A9QI4-KRLmb57HzD2zRqPEXeEMPZBKSouqF90kcARqsOthaawXdll1TGlobl7pe_ncESif3E4wY2C3hn67SYskNqlvy48K_km

  1. Make sure the C•CURE 9000 Victor Web Service is enabled, licensed and accessible from the machine the Proxyclick client will be installed on.
  • The documentation from C•CURE 9000 should guide you on how to set this up Note: You can host the Proxyclick client on the same server as the Victor Web Service.
  1. The default connection port for the Victor Web Service is port 80. This port (or an alternative if this has been changed from the default) will need to be opened in the firewall of the machine itself, as well as any intermediate firewalls between Victor Webservice and the Proxyclick client.
  • We highly recommend you run this over an encrypted HTTPS connection.
  1. Follow this link to find out if the Victor Webservice is running and accessible by us (replace "example.com" with the domain in use for C•CURE 9000):

    http://example.com/victorwebservice/

    If this URL isn’t accessible and you’ve followed all steps within the C•CURE 9000 documentation, please contact C•CURE 9000 tech support for assistance. The website should look similar to this:

clipboard_e32cb6dcb43ce48e14297d0565c1013d3.png

CHUID and Card Format - for QR-based access

Follow the advice in our QR code setup then apply the correct CHUID and card format in C-Cure.

Create a CHUID to be used for the Proxyclick C-Cure integration. Name this exactly as "Proxyclick QR code" (minus the quotation marks) and we will automatically make use of it.

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. See Access Card Manager.

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

Ensure Timespan of Expiration is set correctly

In CCure 9000 Administration Station, see Options & Tools > System Variables Proxyclick doesn’t add an expiration by default, so ensure the "Timespan of Expiration" is less than 2038 minus the current year.

CCure enforces a limit for the expiration, so this cannot be further in the future than 2038 - if this option was set to 20 years this would pass the 2038 limit and fail.

Example: in 2020 do not have a Timespan of Expiration greater than 17 years.

Ensure multiple credentials per person are allowed

Proxyclick creates one credential per meeting, so multiple credentials per person will need to be configured (Maximum Cards Per Person). Set this value to a reasonable amount.

C•CURE operator

For the Proxyclick integration to work we need user credentials to be able to log into the Victor Web Service. This user can either be an internal or directory account.

  • The Privilege should be System all, always.
  • Make sure to tick the enabled box.

We recommend using a long, strong password and to not communicate this with anyone over email. Simply set this up with a Proxyclick employee while configuring the integration, so the details are not stored anywhere.

clipboard_ef64852da9678d091c7cbc979146e563a.png