- This line was added.
- This line was removed.
- Formatting was changed.
This article describes how to configure the RCO R-CARD M5 Admin API Service, to enable integration between the Smart ID Physical Access component in Smart ID Identity Manager and RCO R-CARD M5 via an Admin API.
R-CARD M5 is an Access Control System provided by RCO and managed via a Restful API. After integration, all administration of Users, Access Token and Entitlements (besides defining them) should be done in Identity Manager, never in R-CARD M5.
For details on which data can be imported and exported from RCO R-CARD M5, see About import and export to Physical Access.
The following prerequisites apply:
Configure RCO Service data fields
The RCO 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.
This group defines how to export card numbers by default, when a card’s layout does not have a specific mapping.
This group contains compound configuration elements using the config_index column. For each unique config_index value in this group, each key defined below must be defined exactly once. Note that this group is not required as a whole, and should only be used if you have specific requirements for one or more card layouts.
Example configuration for card mapping settings:
This article is valid for Smart ID 2122.10.1 04 and later.