Deploying and configuring SAFR and Lenel S2 OnGuard for Cardholder synchronization will allow SAFR to import cardholder data and access credential from Lenel OnGuard to be used on SAFR SCAN face authentication readers. SAFR Identity synchronization is a one way synch from OnGuard to SAFR. SAFR SCAN uses the imported face image, converted into a biometric signature, to verify a person identity when presented at a SAFR SCAN reader. When a person’s identity has been verified, the SAFR SCAN reader transmits the imported Access Credentials to the access control panel via Wiegand or OSDP.
Please note that SAFR will not import a person record if it does not have a card access credential. Likewise, if the access credential is removed from the person record, SAFR will delete the person record in SAFR. SAFR only supports one card access credential per person record. If multiple credentials exist, the most recently updated credential is imported.
For complete SAFR and SAFR SCAN documentation please visit http://docs.real.com.
Integration between SAFR – Lenel S2 OnGuard is available on SAFR Platform running Windows.
This guide specifically describes:
A typical integration architecture:
Please note that this Guide does not include the Installation of the SAFR Server (SAFR Platform) or the Lenel S2 OnGuard system.
Lenel S2 OnGuard has the following system requirements:
Note: Lenel give licenses only to its customers if integration is certified by Lenel. SAFR is certified on versions 8.1 and 8.2.
SAFR has the following system requirements:
The following is the current imported and supported attributes/field from OnGuard
OnGuard |
SAFR (People data record) |
Notes |
First Name |
First Name |
|
Last Name |
Last Name |
|
Badge Type |
Person Type |
|
A hidden field (LNL_Person.ID) |
External ID |
|
Card holder Picture |
Picture |
? If no picture in person record, import only name and credentials for use with card only access. |
Activate Date (LNL_Badge.ACTIVATE) |
Access Activation |
Records are not added until Active Date is reached. |
|
||
|
||
Deactivate Date |
Access Expiration |
SAFR Expiration set to same if before Deactivate Date. If after Deactivate date, record not added. |
n/a |
Access Card Facility ID |
Facility ID is the Facility ID entered in the SAFR configuration of External Synchronization. |
Badge ID |
Access Card ID |
If Cardholder has multiple credentials, the most recently added or modified will be imported. |
Card Format |
Access Card Format |
Card Format is set on the reader in both Lenel and SAFR independently. At least one of the card formats in Lenel OnGuard must match the card format set in on the SAFR SCAN device. Card format is not set on each person record when using Lenel OnGuard integration. |
n/a |
Access Information Origin |
Safr sets to “Lenel” |
n/a |
Last Origin Synch Date |
Last time the record was updated in SAFR. |
A license thru Lenel must be obtained for SAFR Integration to OnGuard. The License part number is IPC-094-RLNET01-B. One Lenel license is required for each SAFR reader. Please work with your Lenel representative to obtain the necessary licensing.
No additional license is required from SAFR for this integration.
SAFR and OnGuard use port 8080 for secure SSL communication and need to be open inbound on the Server hosting OnGuard.
A SAFR user must be defined in OnGuard’s “Users” tab with sufficient permissions to allow SAFR to connect and retrieve Cardholder data.
A user defined and configured in OnGuard with the following minimum Permission Groups rights.
In OnGuard System Administration Application, ensure “Generate software events” is checked under the configuration of the OpenAccess host.
A badge status should be assigned to badges after the deactivate date.
To set up identity synchronization between SAFR and Symmetry, do the following:
Check the Set up External Identity synchronization box. The following dialogue will appear:
SAFR SCAN must be connected to the panel as described below.
External Identity synchronization with LenelS2 are customized via configuration file. Available properties are documented in lenel.properties as described below. To ensure configuration changes are persisted during SAFR upgrades, place any customized properties into the persistent.overrides.properties file.
To view available configuration options along with documentation on their behavior: