Plugin cannot synchronize with Siemens SiPass - SiPass 3.4.0

Siemens SiPass Plugin Guide 3.4.0
Product
SiPass
Content type
Guides > Plugin and extension guides
Version
3.4
Release
3.4.0
Language
English
Last updated
2023-08-11

If you see that some SiPass entities or events are missing in Security Center, or that the synchronization does not occur at all, you may want to start a synchronization manually.

Ensure that a connection is established between Security Center and the SiPass server and that the plugin role does not show a yellow warning.

Synchronization issues typically occur when the SiPass plugin and the SiPass server run incompatible versions, or when a disconnection occurs while a synchronization is in progress.

Incompatible versions

Solution: Make sure that the plugin and the SiPass server versions are compatible.

Entities not available

Solution: Ensure the entities have been properly synchronized and are available in Security Center.
  1. From the homepage in Config Tool, open the Plugins task.
  2. In the Plugins task, select the SiPass plugin from the entity browser, and click the Synchronization tab.
  3. Click the Refresh () button under Currently synchronized entities, and verify that the number of entities currently synchronized matches the number of entities (objects) in SiPass that are eligible for synchronization.
  4. If the number of entities does not match, or if there is no entity at all being synchronized, click Start synchronization to start a manual synchronization.
    The synchronization progress and the number of entities being synchronized for each type of entity is displayed under Latest synchronization information.
  5. Under Latest synchronization information, make sure that the synchronization completed successfully.

Connection issues

Solution: If the issue persists, try the following:
  • Restart the plugin role.
  • Restart the server on which the plugin role is running.
  • Restart the SiPass proxy service.
    NOTE: Restarting the proxy service triggers a full synchronization with the SiPass server, which might take a long time to complete depending on the number of entities that must be synchronized.

Credential collisions

Card credentials with the same card format and values synchronized from SiPass cannot already exist in Security Center.

Example: If you have a Corporate 1000 card with facility code 2 card number 6 in SiPass, the card can be synchronized to Security Center only if there is not already an existing Coporate 1000 card with facility code 2 card number 6 enrolled in Security Center.

Solution: Remove the credential causing the conflict from Security Center.

Browse