...

iSecure is an Access Control System provided by Security Shells and managed by a GUI and the service interacts with iSecure through the web-based iSecure API. iSecure is used to integrate with all versions of the HID access controllers VertX and EDGE. After integration, all administration of Users, Access Token and Entitlements (besides defining them) should be done in Identity Manager, never in iSecure. 

For details on which data can be imported and exported from iSecure, see About import and export to Physical Access.

...

• Physical Access and the iSecure Docker container/service are installed. See Deploy Smart ID.

• iSecure S/W Version-E-A2.4-Unlimited CI - 60 is required. 

• The message queue server must be running.

• If MIFARE card technology is used, the PACS MIFARE number must be available as raw data (not encrypted, truncated, or similar). 

• A working network connection to the connected physical access control systems (PACS) must be in place.

Limitations and constraints

...

• In iSecure, only one card can be assigned per employee. If the Physical Access service finds more than one card to one employee which matches the configuration, then the old assigned card will be replaced with the new. 

• Before a card can be assigned to an employee, it must be available in the iSecure system and must match the card format.
  → See the section Create Card in iSecure below.

• The following employee fields in iSecure are required: Emp Code, Company, Location and Department. Emp Code shall contain any unique data from user records, other fields can either be static in the configuration or mapped as user additional fields.

...

The iSecure 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.

...

...