This article describes how to configure the Interflex Service, to enable integration between Smart ID Identity Manager, Physical Access and the Interflex Service.
Interflex is an Access Control System provided by Interflex Datensysteme GmbH and managed by a GUI and API to interact with Interflex. After integration, all administration of Users, Access Token and Entitlements (besides defining them) should be done in Identity Manager, never in Interflex.
For details on which data can be imported and exported from Interflex, see About import and export to Physical Access.
Prerequisites
Configure Interflex Service data fields
The Interflex data is configured in the configuration table in the Physical Access database. All configuration is cached when the service starts so any configuration changes will require the service to be restarted in order to take effect.
To connect to a PACS system:
- Log in to Physical Access admin panel as an admin user.
All configured PACS connector services are listed, as well as Generic configurations to define the messaging queue. - Click on a system to do updates.
All database entries are listed. - To update an entry, click on the icon
. Edit as needed and then click Update. - To create an entry, click on +Create. Select Group, enter Key, Value and Index, and then click Create.
group: messagingqueue
| key | Data type | Required or Optional | Description |
|---|---|---|---|
| server | string | Required | IP Address of Message Queue Server. If it is installed on the local server then we can use localhost. If we are accessing this server remotely then need to mention IP address. |
| username | string | Required | Username of message queue server. Default value: “guest” |
| password | string | Required | Password of message queue server. Default value: “guest” |
| system | string | Required | Defines which messaging queue to be used, either "rabbitmq" or "azureservicebus". Default value: "rabbitmq" |
group: general
| key | Data type | Required or Optional | Description |
|---|---|---|---|
| deleteUserOnNoEntitlement | string | Optional | Defines if the user shall be deleted if no active entitlement assignment are present for that user. Valid values: Default: |
| deleteUserOnNoAccessToken | string | Optional | Defines if the user shall be deleted if no active access tokens are present for that user. Valid values: Default: |
heartbeatInterval | int | Optional | Heartbeat interval is the time difference between two successive heartbeats, and it is used to know if the system is in active (running) or in inactive (stopped) state. Default value and minimum value: 60 seconds. If it is set less than 60 seconds, it will be considered as 60 seconds to update the status. |
group: general
| key | Data type | Required or Optional | Description |
|---|---|---|---|
| updatesPerPoll | int | Optional | The maximum number of messages read from the message queue. Default: 100 |
group: interflex.system
| key | Data type | Required or Optional | Description |
|---|---|---|---|
| systemId | string | Required | System id is a unique value which is sent with a request to identify rest client on server. Default: “PHYSICAL-ACCESS-INTERFLEX-CLIENT” |
| username | string | Required | Username to login into IF-6040 Rest API |
| password | string | Required | Password to login into IF-6040 Rest API |
group: interflex.general
| key | Data type | Required or Optional | Description | ||||||
|---|---|---|---|---|---|---|---|---|---|
| apiUrl | string | Required | Base URL of IF-6040 rest API endpoint to import access element and export user details. | ||||||
| entitlementImportTypes | string | Required | EntitlementImportTypes is used to set which type of access elements Physical Access should import. Currently, these entitlementImportTypes are supported:
To have support for both types, add it like “AccessProfile, AccessZoneTimeProfile”. | ||||||
| organizationUnit | string | Required | OrganizationUnit is the name of the default organization which can be used to create User or Card. |
group: interflex.export
| key | Data type | Required or Optional | Description |
|---|---|---|---|
| cardNumberIdentifierType | string | Required | This is a type of identifier in an access token. This setting indicates which type of identifier that is used for card number. Default: “mifare”. |
| userIdentifierPrefix | string | Required | A prefix which is appended before Personnel Number of Person in Interflex. Default: “PA”. |
group: export
| key | Data type | Required or Optional | Description | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| userfieldmappings | string | Optional | The userfieldmappings is the combination of all additional fields that can be sent to Interflex. Currently, these fields can be configured:
To export these fields to Interflex, add this configuration:
The value in the configuration setting is a combination of table_name.value_of_type_column, property_name_of_cardholder. This configuration setting is the mapping between PA3 table field and Interflex cardholder model properties. User column fields are sent by adding configuration like user.column_name_of_user_table, property_name_of_cardholder. |
Restart service
This article includes updates for Smart ID 23.04.2.
Related information
Integrate physical access control system (PACS) with Identity Manager