To connect to a remote Security Center system
using Security Center
Federation™, you must create and configure a Security Center
Federation™ role on your system, using the credentials for your
Federation user.
Before you begin
Ensure you have the username and password of the
Federation™ user, created for you by the administrator of the system
you want to federate. The rights and privileges of the
Federation™ user determine what the users on your system can see and
do on the federated system. The
Federation™ user must have
the application privilege
Federation™ and any other
privilege you need to perform your task.
Procedure
-
Open the System task and click the Roles
view.
-
Click Add an entity (), and
click Security Center
Federation™.
-
In the Directory field, enter the name or IP address of the
remote Security Center Directory.
-
Enter the username and password for the Federation™
user, that the Federation™ role is going to use to log on
to the remote Security Center system.
-
In the Federated events section, select the events that you want
to receive from the federated system, and click Next.
-
In the Basic information page, enter a name and description for
the role.
-
Select a Partition this role is a member of, and click
Next.
All federated entities are created in the partition you select. Only users that are
part of the partition can view or modify those entities.
-
Click .
-
Select the new Federation™ role (), and click the Properties tab.
The connection status should say Synchronizing entities, or
Connected.
-
Decide what happens if the connection between the Security Center
Federation™ role and the federated Security Center Directory is interrupted by configuring
the following options:
- Resilient connection
- When this option is turned on (default=OFF), if the connection between the Federation™ role and the federated Security Center Directory server is temporarily
interrupted, the Federation™ role attempts to reconnect
to the Directory for a set amount of time before the connection is considered lost and
the role goes into a warning state.
NOTE: Activating Resilient
connection is highly recommended for remote systems that might have an
unstable connection to the cloud.
- Reconnection timeout
- Specify the number of seconds that the Federation™
role attempts to reconnect to the Directory before the connection is considered
lost.
-
Configure the additional options for Security Center
Federation™:
- Forward Directory reports
- When this option is turned on
(default=OFF), you can view user activities (viewing cameras, activating the PTZ, and
so on) and configuration changes performed at the federated site from the
Activity trails and Audit trails reports
on the Federation™ host, as long as the Federation™ user has the privileges and access rights to
view them.
IMPORTANT: Forward Directory reports is only supported with
5.8 systems and higher (including federations). This means that if your federated
system is 5.7 and lower, the Forward Directory reports option is grayed out and not
available.
- Default live stream
- Default video stream used for viewing live video from federated Security Center cameras
(default=Remote).
If your workstation does not require
specific video stream settings for Federation™, you
can use the default stream settings from Security
Desk instead.
- Enable playback requests
- When this option is turned on, users can view playback video from federated Security Center cameras.
- Federate alarms
- When this option is turned on, alarms are received from the federated Security Center system.
-
Click Apply.
-
If necessary, change the default multicast addresses used by the Media Router for local
and federated streams.
After you finish
In the
Area view task, expand the
Security Center
Federation™ role (
) and make sure all the federated entities were imported by the
role.
The entity hierarchy corresponds to the area view on the federated remote
system.