SALTO ACS#
The ACS synchronizes employees with the list in Luna and listens to events, based on which it decides whether or not to open the turnstile. These events are generated in Access by the SendToSalto pipeline.
- Supports Salto ACS version: 6.6.3.0.
Replicates user data from the Salto database to the specified Luna list and generates SaltoController controllers from the resulting list of access points for subsequent execution of access requests.
For the configuration of the Salto ACS, see the official documentation.
Supported integration options for SALTO ACS#
The face recognition device generates an event, Access passes the event to LP5, LP5 processes the event and returns the result to Access for further processing.
User data is transferred from the ACS to LP5 using two mechanisms:
- replication - the mechanism for the initial transfer of user data;
- synchronization - the mechanism for periodic transfer of user data when the composition/data of users changes.
Each integration with LP5 (Table 56) uses the Luna service.
Table 56. LP5 integration options
Standard integration using Salto#
Salto integration (Figure 92) and (Table 57).
Table 57. Integration description
| Component | Description |
|---|---|
| Person | A person wishing to pass through a passage point. |
| Passage point | A set of components used to control human access. More than one passage point can be connected, limited by the ACS license. A passage point can be used for both entry and exit. Each direction uses its own reader and video data source. |
| Video source | A device for extracting a frame of a person's face. Can be either a biometric terminal (LUNA FAST 4A1 and others). A biometric terminal allows you to create feedback to show a person information about the passage. |
| Turnstile | A barrier device for access control |
| SALTO ACS | Central software for working with Salto. Stores employee data and makes a decision on granting access. |
| Device ... | An Access component for receiving data from a video data source. Selected based on the device used. |
| SaltoController Controller | Access Component for sending the card number to the ACS. |
| SendToSalto Pipeline | Access Component for exchanging data with the ACS and transmitting data for display on the device screen. |
| MatchByPhoto Pipeline | Access Component for interacting with the BS. |
| Salto Service | Access Component for replicating/synchronizing employees from the ACS and listening to ACS events. |
| Biometric System | A system for comparing a reference photo of a person and the best frame received from a video data source. Luna is supported. |
SALTO ACS Access Levels#
SALTO ACS integrated with LUNA Access has a flexible access level system.
Access levels can be assigned to both doors and employees. Each employee and each door can have a list of access level identifiers.
Information storage:
-
Door access levels are stored in the info field of the corresponding controllers in LUNA Access.
-
Employee access levels are stored in the local person storage.
Access check:
When attempting to open a door, LUNA Access compares the employee and door access levels. The door will only open if the employee has at least one access level that matches one of the levels assigned to the door.
Integration features:
The request to open the door is sent to SALTO ACS in an anonymous form. The ACS passage events do not display who exactly passed through using biometrics - the event is recorded as the opening of the door by the ACS operator.
Methods for interacting with Salto#
Start of endpoint for all requests (Table 58), except authorization: /rpc
Table 58. Salto methods
| Task | Method | Description |
|---|---|---|
| Authorization endpoint | /oauth/connect/token | Request for ACS authorization token. Authorization occurs when adding a service |
| Get ACS version | POST /GetBootstrapConfiguration | Get ACS version |
| Get ACS access points | POST /GetDoorListStarting FromItem | Request for getting ACS access points |
| Get a list of employees in ACS (replication) | POST /GetUserListStarting FromItem | Request to obtain a list of all employees in the ACS |
| Get a list of events in the ACS (synchronization) | POST /GetStatusOfGetSystem AuditorEventList | Request to obtain a list of the latest events in the ACS |
SALTO interaction process diagram#
Sequence diagram (Figure 93).
1․ The user added the Salto service to Access. 2․ Access sends a request to obtain an authorization token to the ACS. 3․ The ACS returns a token for authorization. The token has a lifetime, after which Access performs authorization again. 4․ Access sends a request to obtain information about the ACS. 5․ The ACS returns information. Access uses only the ACS version to check compatibility and display the version in the UI. 6․ Access sends a request to obtain access points created in the ACS. 7․ The ACS returns a list of access points. 8․ Access creates SaltoController controllers according to the received IDs. 9․ Access sends a request to obtain a list of employees in the ACS. 10․ The ACS returns a list of employees. 11․ Access saves information on each employee to the local storage. 12․ Access sends a request every 10 seconds to receive events about employee changes to perform synchronization. 13․ ACS returns events. 14․ Access adds/updates information on each employee to the local storage.