- This line was added.
- This line was removed.
- Formatting was changed.
This article describes how to install and configure the Unison Pacom Service, to enable integration between Smart ID Identity Manager (PRIME) PACS Backend and Physical Access and Unison Pacom.
Unison is an Access Control System provided by Pacom and managed by a GUI and a web service on the server and the service interacts with Unison through the wcf service.
After integration, all administration of Users, Access Token and Entitlements (besides defining them) should be done in Nexus PRIMEIdentity Manager, never in Unison.
For details on which data can be imported and exported from Unison Pacom, see About import and export to Physical Access.
The following prerequisites apply:
Configure Unison Pacom Service
The service is configured in the configuration table in the PACS Backend Physical Access database and in the configuration file. All configuration is cached when the service starts so any configuration changes will require the service to be restarted in order to take effect.
The configuration file is named UnisonService.exe.config.
The optional setting cardformatmappings can be used to configure access profiles. If cardformatmappings is used, then all its settings are required to be configured, otherwise the connector will throw an error. This setting directly depends on the setting
The table below shows a sample configuration of an access profile called Standard Magnetkort. The access token identifiers are configured in the following way:
This mapping is used to export values of user related objects such as User, Email, Address, Phone and Useradditionalfields table fields to Unison fields. For exporting user table fields configuration settings will be combination of Table_name.column_name, field_id_of_Unison and for rest of the table it will be Table_name.value_type, field_id_of_Unison.
The service mainly transfers user data including related access tokens and entitlement assignments. The tables below show the default field mapping.
If needed, additional fields can be configured, using the SCIM API and
User field mapping
By default, the following data is mapped between the USER table in the PACS Backend Physical Access and the Unison service:
Access token field mapping
By default, the following data is mapped between the ACCESSTOKEN and ACCESSTOKENIDENTIFIER tables in the PACS Backend Physical Access and the Unison service:
Entitlement assignment field mapping
By default, the following data is mapped between the ENTITLEMENTASSIGNMENT table in the PACS Backend Physical Access and the Unison service:
Install Unison Pacom service
The installation file is named UnisonService.exe.
Restart Unison Pacom service
The service SystemId is Unison.