Skip to main content

 

Eptura Knowledge Center

Nedap AEOS Configuration

  1. Last updated
  2. Save as PDF

Within AEOS your visitors will be created with templates and identifiers to allow your Proxyclick visitors to gain access. The Proxyclick <> Nedap AEOS 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.
  • The access control API listens on port 8443 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.

Install AEOS with SOAP webservice

Refer to the AEOS SOAP WebService documentation to ensure your AEOS instance is installed with the SOAP capability.

Enable the SOAP webservice

Make sure to go to Administration / Settings / System Properties and tick option 44.15 "Soap Webservice".

You will have to restart your AEOS services after changing this setting.

clipboard_e7dc26b1dbc97bcf7e6228ab3068b2edd.png

Ensure the webservice is reachable

The AEOS webservice needs to be reachable from the machine the Proxyclick client will be installed on. You can confirm this by accessing the url: https://example.com:8443/aeosws. - Replace example.com with your hostname or IP address.

It should return an error document similar to the below image.

clipboard_eaabc9580c38a56f9e946f711b36b7bee.png

Identifier type - for QR-based access

An identifier type needs to be set up within AEOS. The name needs to be exactly written as follows (without the quotes): ‘Proxyclick QR code’.

The below sample is set up to read the default format, contact your installation partner for support to ensure the QR is read correctly by the hardware.

clipboard_e2bf854df8ef950d85bedb6991ead8dec.png

clipboard_ea98083da2b5fe8b1338acb69866f8c54.png

clipboard_eb288633950cbd7c953eb26e5f35dc15b.png

clipboard_ed368599d7cdd93e4f2eba419108218da.png

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 configured for your RFID readers. See Access Card Manager.

Note: QR code setup steps (create and configure the Proxyclick Identifier Type) must be completed to enable the use of physical credentials.

Operator setup

Set up an Admin operator for Proxyclick to use in AEOS. The username and password should be entered when connecting the Proxyclick AEOS access client to Nedap AEOS.

Template setup

The Proxyclick integration will automatically manage the setup of templates.

Refer to the Access Control Overview for more detail on what type of access should be granted for each of these templates.

Entrance setup

For Proxyclick to be able to check visitors in or out when access is granted, a list of entrances need to be provided. The list should be separated by direction (in or out).