Skip to main content

 

Eptura Knowledge Center

Galaxy Configuration Requirements

  1. Last updated
  2. Save as PDF

Coming soon!

The Proxyclick Galaxy integration is expected in February 2025.

The following prerequisites are required for the Galaxy integration:

 

Prerequisites and recommendations

 

Networking

  • The Proxyclick access control client reaches out to Proxyclick servers via port 443. Learn more: Deployment requirements for access control integrations. 
  • By default, the access control API listens on port 8000, but your configuration might be different. We recommend confirming the correct port number with your access control administrator.
  • The Proxyclick access control client must be able to reach the API.

 

Enable the REST API

An API key is required for the Proxyclick client to talk with your Galaxy server. 

Contact Galaxy to obtain an API key. Make a note of the key as you will need it to configure Proxyclick client later.

 

Create a Proxyclick operator

We recommend running the Proxyclick client with a Galaxy specific operator. 

Create an operator with the name 'Proxyclick Service Account' (recommended) in Galaxy via Configure > System > System Operators. 

We suggest naming the operator 'Proxyclick Service Account' to avoid any confusion about its purpose and to prevent its deletion in the future.

Assign the 'Master' permissions to this operator account and apply a password.

The password for the operator account is only used by the Proxyclick client software and is entered by yourself. You do not need to share the credentials with Proxyclick directly.

 

QR reader setup and testing

Token numbers (ID Codes) relating to Proxyclick QR Codes are entered in the format 'HID 37 bit H10302 ID Code Only'

Your Wiegand output QR reader must be set to output the correct format as selected for the credential types in use by Galaxy. Various Wiegand output formats are available to select. Learn more: QR code reading hardware

If you add the token number as a card in Galaxy using the format 'HID 37 bit' (for example) you must ensure the reader is configured to send 37 bits of data to your controller.

  1. Set up a test user in Galaxy.
  2. Add the token number as a card. Example codes are available in Reader output format: for testing your reader
  3. Select the card format suitable for your reader's output settings.
  4. You can now assign the card to your test user in Galaxy.

Ensure the test user has an access level that allows access - you can then use the test QR code from our documentation to ensure the reader is working as expected.

Share the Wiegand format with your Proxyclick/Eptura contact so we can ensure our integration inputs tokens in the correct format.

 

Using physical credentials - RFID cards/fobs

If using our Access Card Manager functionality to issue physical RFID credentials via Proxyclick, share the card format / facility code with your Proxyclick/Eptura contact

 

Access levels

Access levels cannot be created automatically in Galaxy.

To allow standard functionality, three access levels must be manually created in Galaxy using the following exact names:

  • Proxyclick expected
  • Proxyclick checked-in
  • Proxyclick checked-out

These access levels, if named correctly, are applied to visitor profiles in Galaxy and correspond to the Galaxy visit statuses: Expected, Checked-in, and Checked-out, respectively.

Custom Access functionality is not yet supported

 

Proxyclick client configuration

On the 'Connection settings' tab, in the Proxyclick client, enter the API key provided by Galaxy and the Company name used in your Galaxy configuration.

You must enter the exact Company Name used in your Galaxy configuration. 

The Proxyclick client can only connect to a single Galaxy server. 

What's next