Fortinet black logo

FortiClient EMS Connector

Copy Link
Copy Doc ID 4d03f4a8-36de-11e9-94bf-00505692583a:147225
Download PDF

FortiClient EMS Connector

The FortiClient EMS Connector works virtually the same way as Active Directory / Single Sign On (FSSO) from the FortiManager's perspective:

  • Configure the connector in FortiManager that manages the FortiGate devices. The administrator can define and install the dynamic groups and policies to FortiGate devices.
  • FortiGate will communicate directly to FortiClient EMS to learn dynamic group changes and apply them in runtime.
To configure FortiClient EMS Connector with FSSO in FortiManager:
  1. Install FortiClient Endpoint Management Server in Windows server. Log on to the EMS server and go to Compliance Verification > Compliance Verification Rules and click Add Rules. Create a few rules with different tags.

  2. Log on to FortiManager. Go to Fabric View > Fabric Connectors and click Create. Select FSSO and click Next.

  3. In the Create New Fabric Connector screen, specify a Name, select the Type as FortiClient EMS, IP/Name as the Windows Server's IP and leave the password blank if the Windows Server does not have a password. Turn SSL to ON.

  4. Click Apply and Refresh. The connector gets a list of tags from the EMS server and shows them as User Groups. This is similar to the Active Directory group in the backend of the Windows Server.

  5. Go to Policy & Objects > Object Configurations > User & Device > User Groups and create a new user group. Specify a name for the group, select the type as FSSO/Cisco TrustSec and in Select Entries, select the tags from EMS server as members. Use this user group in a policy and install the policy to FortiGate devices.

  6. The Fabric Connectors are also visible in Policy & Objects > Object Configurations > Fabric Connectors > SSO/Identity where they can be edited if required.

Note

Refer to FortiClient Enterprise Management Server (EMS) Administration Guide or FortiClient Enterprise Management Server (EMS) Release Notes for system requirement and versions of Windows Server supported.

FortiClient EMS Connector

The FortiClient EMS Connector works virtually the same way as Active Directory / Single Sign On (FSSO) from the FortiManager's perspective:

  • Configure the connector in FortiManager that manages the FortiGate devices. The administrator can define and install the dynamic groups and policies to FortiGate devices.
  • FortiGate will communicate directly to FortiClient EMS to learn dynamic group changes and apply them in runtime.
To configure FortiClient EMS Connector with FSSO in FortiManager:
  1. Install FortiClient Endpoint Management Server in Windows server. Log on to the EMS server and go to Compliance Verification > Compliance Verification Rules and click Add Rules. Create a few rules with different tags.

  2. Log on to FortiManager. Go to Fabric View > Fabric Connectors and click Create. Select FSSO and click Next.

  3. In the Create New Fabric Connector screen, specify a Name, select the Type as FortiClient EMS, IP/Name as the Windows Server's IP and leave the password blank if the Windows Server does not have a password. Turn SSL to ON.

  4. Click Apply and Refresh. The connector gets a list of tags from the EMS server and shows them as User Groups. This is similar to the Active Directory group in the backend of the Windows Server.

  5. Go to Policy & Objects > Object Configurations > User & Device > User Groups and create a new user group. Specify a name for the group, select the type as FSSO/Cisco TrustSec and in Select Entries, select the tags from EMS server as members. Use this user group in a policy and install the policy to FortiGate devices.

  6. The Fabric Connectors are also visible in Policy & Objects > Object Configurations > Fabric Connectors > SSO/Identity where they can be edited if required.

Note

Refer to FortiClient Enterprise Management Server (EMS) Administration Guide or FortiClient Enterprise Management Server (EMS) Release Notes for system requirement and versions of Windows Server supported.