STid Integration
Overview
STid is a French manufacturer specializing in high-security contactless identification solutions. The Integriti platform provides native integration for STid Mobile ID credentials and a wide range of STid readers, including Architect® series, biometric, and government-grade hardware.
Technical Details
Integration Methods
STid readers can be integrated with Inner Range host modules (IAC, ILAM, SLAM) using several communication protocols:
- OSDP (Open Supervised Device Protocol): Recommended for high-security sites, providing encrypted bi-directional communication.
- Wiegand: Supported for legacy or standard deployments.
- STid Mobile ID API: Integriti uses STid APIs (v3.0) to manage the issuance and revocation of virtual credentials directly from the management software.
Hardware & Card Support
- Supported Readers: Architect® series, biometric readers, and standard smart readers.
- Credential Compatibility: Supports STid smart cards (DESFire EV2/EV3), virtual mobile credentials (via BLE/NFC), and standard 13.56MHz MIFARE cards.
- Unicity: Integriti enforces global uniqueness for STid credentials. A registration request will be rejected (Error 409) if a credential ID already exists in the cloud or Integriti database.
Configuration (Integriti)
Prerequisites
- Integriti Edition: Business or Corporate.
- Integriti Version: V24 or higher.
- Product License Version: V25 or higher.
- License Part Number: 996964 — Mobile Credential Management Integration license.
- STid APIs: v3.0 (works with any STid cloud version supporting this API).
STid Cloud Setup
- Obtain a Client ID when signing up with STid services.
- Use the Client ID to generate a Client Secret.
- Create at least one Site on the STid cloud with a Card Profile assigned.
- Only one card profile can be associated per site; the same card profile can be used across multiple sites.
- Card profiles are created using the SECard application (contact your STid representative).
- Each Site–CardProfile combination becomes a Mobile Credential Pool in Integriti.
- Global Uniqueness: Optionally configure in STid cloud (Panel → Settings → Advanced). When enabled, duplicate credential IDs across sites are rejected (Error 409). Integriti always generates globally unique credential IDs regardless of this setting.
Integriti Integration Module
Add the STid Mobile Credential System integration module and configure:
| Parameter | Description |
|---|---|
| Server Hostname | Pre-configured STid Mobile ID web server hostname. Do not change. |
| Client Id | Client ID from the STid account portal. |
| Client Secret | Client Secret used to authenticate to the STid Mobile Credential Web Service. |
| State Processing Interval (s) | How often Integriti polls for card state changes from STid (in seconds). |
Logging
| Parameter | Description |
|---|---|
| Log Verbosity | Only logs at or above the selected level are written. |
Invitations
| Parameter | Description |
|---|---|
| Invitation Link | STid Invitation Link. The invitation code is inserted in place of the UID placeholder. |
AirCut Mode (v2.1+)
A ‘try-before-use’ safety feature. When On, Revoke/Delete commands are only traced (not sent to the cloud). Default is Off and the parameter is hidden (Visible-On-Demand) — type a in the search field to reveal it. AirCut traces appear in Integriti Log and DebugView.
Refreshing Mobile Credential Pools
Press the Refresh Mobile Credential Pools button with one of these options:
- Full — Full refresh.
- Add Or Update Only (No Delete) — New pools added; removed pools remain in Integriti; names updated.
- Update Only — Updates names only.
- Add Only — Adds new pools only.
Connection Restart
Force a reconnection between Integriti and STid. Use after initial setup or configuration changes.
Operational Considerations
- Online/Offline: After installation, the plugin shows offline with an error — this is expected. Run Refresh (full) to clear.
- Multiplicity: A user can have strictly one credential per pool. Multiple credentials of the same card profile are allowed across different pools.
- Revoke/Delete: Deleting a credential returns credential credits. Revoking sets state to
RevocationPending; Integriti periodically scans and auto-deletes credentials once they reachRevokedstatus. - Credential Life Cycle: A credential can be deleted and a new one issued for the same pool immediately.
Core Capabilities
| Feature | Description |
|---|---|
| Generate credentials for a user | Create and populate newly generated credentials into Integriti. |
| Revoke credentials from Integriti | Cancel invitations or revoke existing credentials via UI, deletion, or user removal. |
| Resend Invitations | Send users email invitations to accept new credentials. |
| Auto-generate credentials | Automatically generate credentials when a user change is detected. |
| Auto-revoke credentials | Automatically revoke credentials or cancel invitations on user change. |
| Display Connection Status | Show whether Integriti is connected to STid. |
| Generate Alerts from Mobile Events | Create/restore Alerts tied to credentials or pools on STid events/alarms. |
| Trigger Integriti Actions | Trigger automations in Integriti on STid events/alarms. |
| Entity Synchronisation | Verify and update users and credentials in STid when Integriti user changes. |
Advanced Capabilities
| Feature | Description |
|---|---|
| Populate Credential Pools | Refreshing child devices populates all configured credential pools into Integriti. |
| Show Card Status | Current status of mobile credentials visible directly in Integriti. |
| Show Credential Pool Status | Pool availability visible directly in Integriti. |
| 64-bit Integration Server Support | Runs on the 64-bit integration server. |
| Categorised Review Records | Different review categories for different integration event types. |
Troubleshooting
- Check STid cloud portal first — every generated credential should be visible with its current state.
- Enable Debug logging level for the plugin in Integriti LogsViewer.
- Use DebugView (Microsoft Sysinternals) to capture developer-grade traces. Run
DebugView64as Administrator and enable Capture → Capture Global Win32.
Error 409
Returned by the STid cloud for:
- Duplicate credential (user with same email already exists in the pool).
- Wiegand26 SiteCode-CardCode credential sent to a pool not configured for that format.
- Non-Wiegand26 credential sent to a pool configured for Wiegand26 format.
Use Cases
- High-Security Sites: Leveraging STid’s EAL 5+ certified hardware and OSDP encryption.
- Biometric Integration: Seamless management of STid biometric readers (Fingerprint/Facial) within the Integriti environment.
- Government/Military: Utilizing STid’s expertise in government-grade identification and secure credential storage.