Siemens SiPass
Siemens·AE_HSc_SiPassConnectorGuide
Overview
The SiPass connector integrates AlertEnterprise Guardian with Siemens SiPass — Siemens' flagship enterprise PACS, widely deployed in financial services, healthcare, and large corporate environments across EMEA. SiPass is the higher-end Siemens PACS; for the smaller / midmarket Siemens line, see siemens-siport and siport-rest.
The architecture is straightforward: AE → ACF → SiPass Connector → SiPass SDK Web Service → SiPass System. The Web Service that the connector talks to is bundled with the SiPass SDK and must be deployed as part of the SiPass installation — it is a hard prerequisite for the connector.
The connector ships as ALNTSiPassConnector-5.0-SNAPSHOT.jar and registers com.alnt.connector.provisioning.services.SiPassHRApiRestConnectionInterface as the extractor class. Despite "HRApiRest" in the class name, the underlying transport with the SiPass Web Service is HTTPS — SiPass exposes its API as a SOAP/REST hybrid depending on operation.
Architecture
Composed from this connector's actors + edges. Trust zones are color-coded; trust crossings render as thicker lines.
Authentication
1 method supported
Authentication uses basic auth credentials configured in the AE connector. SSL/TLS is required between AE and the SiPass Web Service — the connector guide documents the standard keytool -importcert procedure to import the SiPass certificate into the AE host's JVM cacerts keystore.
Prerequisites
Everything that must be in place for this connector to work, with the owner who's responsible.
SiPass SDK Web Service deployed
customerThe Web Service bundled with the SiPass SDK must be deployed and reachable from the AE application server. This is a hard prerequisite — the connector does not talk to SiPass directly.
SiPass operator account with API access
customerA dedicated SiPass operator account with sufficient privileges for the integration's provisioning + reconciliation operations.
SSL certificate trust
aeSiPass Web Service certificate imported into the AE host's JVM cacerts keystore. The connector guide documents the keytool procedure followed by a restart of the Job and API services.
Known limitations
Documented constraints to set customer expectations before deployment.
Web Service must be SDK-deployed (no off-the-shelf REST endpoint)
informationalUnlike vendors that ship a REST API as part of the product, SiPass requires the customer to deploy the SDK Web Service explicitly. This adds deployment complexity and a license-side dependency on the SiPass SDK module.
PACS specifics
SiPass models cardholders with associated badges and access levels. Reconciliation supports User / User Badges / User Access Levels full + incremental.
Access is granted via SiPass Access Levels assigned to badges. Full + incremental reconciliation of access levels is supported.
Single SiPass instance per AE→SiPass connector.
- Topology
- on-prem
- Event model
- polling
- Anti-passback
- unknown
- Holiday schedules
- unknown
- src/connectors/si-pass/source.pdf — Full connector guide — 33 pages, updated 2024-12-17
- src/connectors/si-pass/source.pdf — p5 — Supported Version
- src/connectors/si-pass/source.pdf — p7 — Connector Architecture