Archibus + Proxyclick Integration

This describes the prerequisites and configuration for the visitor integration.

Prerequisites

  1. Establish a Service User Account with Proxyclick that is an Admin.

  2. In Proxyclick, create companies at different locations which can be imported into the Archibus and mapped to Archibus buildings by Archibus Admin.

  3. Establish user accounts in Proxyclick for any employees on the Archibus side that will be creating meetings. This is so that the Host in Proxyclick can be populated for the meeting:

  4. The Eptura User accounts and the Archibus employees and their users have to have the same email address, so that we can match them. The user name can differ, between the 2 systems.

  5. Eptura Service User Account and the Eptura users for the Hosts should have default access to the companies/locations in Proxyclick in order to be able to create/view/modify meetings on that location.

  6. Below are the rights under default access.

visitor_integration_rights.png

Archibus Web Central Configuration Steps

  1. Locate the file: [application directory]\WEB-INF\config\context\applications\reservations.properties file

  1. Set the properties for authentication:

proxyclick.auth-provider.clientId : client id provided by Proxyclick during registration

proxyclick.auth-provider.clientSecret : client secret provided by Proxyclick during registration

proxyclick.baseUrl : URL of the Proxyclick API.

proxyclick.serviceAccountPassword : Password of Proxyclick Admin account

proxyclick.serviceAccountEmail : Email of Proxyclick Admin account

Note:

  • Since, we are using HTTPS for api communication, it is considered as safe as it encrypts the data we are providing. Additionally it uses SSL/TLS certificates to prevent interception. (If we want to add extra encryption at our end same needs to be implemented at Proxyclick end too, for decryption.)

  • Proxyclick is using OAuth for authentication. It is generally used for user-centric authorization where user grants access of their resource to third party application like us. That is why user credentials might required along with clientId and clientSecret.

  1. Set the following deployment option in the reservations.properties configuration file.

reservations.configurationFile=classpath:com/archibus/app/reservation/proxyclick-integration-context.xml

  1. Re-launch Archibus Web Central.