Fortinet black logo

EMS Administration Guide

Home FortiClient 7.2.4 EMS Administration Guide
7.2.4
7.2.4
7.2.3
7.2.2
7.2.1
7.2.0
7.0.12
7.0.11
7.0.10
7.0.9
7.0.8
7.0.7
7.0.6
7.0.4
7.0.3
7.0.2
7.0.1
7.0.0
6.4.9
6.4.8
6.4.7
6.4.4
6.4.3
6.4.2
6.4.1
6.4.0
6.2.9
6.2.8
6.2.7
6.2.6
6.2.4
6.2.3
6.2.2
6.2.1
6.2.0
6.0.8
6.0.6
6.0.5
6.0.4
6.0.3
6.0.2
6.0.1
6.0.0

SAML SSO with AD FS as IdP

SAML SSO with AD FS as IdP

You can configure a single sign on (SSO) connection with Active Directory Federation Services (AD FS), where AD FS is the identity provider (IdP) and FortiClient EMS is the service provider (SP). This feature allows users to log in to EMS by logging in with their AD FS credentials.

The following instructions assume that you have already installed and configured AD FS.

To configure SAML SSO with AD FS as IdP:
  1. In FortiClient EMS, go to Administration > SAML SSO. Service Provider Settings displays the SP Address, SP Entity ID, and SP ACS (login) URL fields. You use these values to configure FortiClient EMS as an SP in AD FS. Copy these values.
  2. Create and configure your FortiClient EMS environment in AD FS:
    1. Open AD FS Management and right-click Relying Party Trusts and select Add Relying Party Trust. This launches the Add Relying Party Trust Wizard. Select Claims Aware and click Next.
    2. In Select Data Source, select Enter data about the relying party manually and click Next.
    3. Enter a Display name and click Next.
    4. In Configure Certificate, leave the certificate settings at their default values. Click Next.
    5. In Configure URL, select Enable Support for the SAML 2.0 WebSSO protocol, then enter the SAML SSO URL obtained from EMS (SP ACS (login) URL).
    6. In Configure Identifiers, enter the Relying party trust identifier URL obtained from EMS (SP Entity ID), then click Add and Next.
    7. In Choose Access Control Policy, leave the default value (Permit everyone) and click Next.
    8. In Ready to Add Trust, review your settings, click Next.
    9. In Finish, select Configure claims issuance policy for this application, then click Close.
  3. Create claim rules:
    1. In the Issuance Transform Rules tab of the Claim Rules editor, click Add Rule.
    2. In Choose Rule Type, select Send LDAP Attributes as Claims from the dropdown list, then click Next.
    3. In Configure Claim Rule, enter a Claim Rule Name, select Active Directory as the Attribute Store, then add the following mapping: from the LDAP Attribute column, select SAM-Account-Name. In the Outgoing Claim Type column, enter Name ID, then click Finish to add the rule. Click OK.
  4. Export the IdP certificate, which you must later upload to EMS to finish SAML configuration:
    1. Open the AD FS management snap-in, select AD FS > Service > Certificates, then double-click the certificate under Token-signing. You can also right-click the field, then select View Certificate in the context menu.
    2. In Certificate, open the Details tab, then select Copy to File and click OK.
    3. In Certificate Export Wizard, click Next.
    4. Select Base-64 encoded X.509 (.CER), then click Next.
    5. In Certificate Export Wizard, select Browse to specify the location to export the IdP certificate to, then specify the file name and click Next.
    6. In Completing the Certificate Export Wizard, click Finish, then click OK to confirm the export succeeded.
  5. Configure the IdP information in FortiClient EMS:
    1. Export the metadata from AD FS by appending FederationMetadata/2007-06/FederationMetadata.xml to the AD FS server root URL. See the following example: https://adfs.domain.com/federationmetadata/2007-06/FederationMetadata.xml. The following shows an example on a local AD FS server: https://localhost/FederationMetadata/2007-06/FederationMetadata.xml.
    2. Obtain the IdP single sign-on URL and entity ID from the metadata. The following shows example values: IdP entity ID: http:/adfs.domain.com/adfs/services/trust IdP single sign-on URL: https:/adfs.domain.com/adfs/ls/
    3. In EMS, under Identity Provider Settings, paste the values obtained from the metadata in the IdP Entity ID and IdP single sign-on URL fields.
    4. Provide the certificate extracted in previous steps.
    5. (Optional) If desired, toggle on Enable Authorization Rules. When this feature is disabled, all SSO users from the IdP can become EMS admin users. When this feature is enabled, only SSO users from the IdP that satisfy a configured rule can become an EMS admin user. To add a rule, click Add. In the Authorization Rule field, enter a username. This field is case-insensitive. Add multiple rules as desired. Only SSO users from the IdP with usernames that match the configured authorization rules can access EMS as an admin user.
    6. Save the configuration.
Previous
Next

SAML SSO with AD FS as IdP

You can configure a single sign on (SSO) connection with Active Directory Federation Services (AD FS), where AD FS is the identity provider (IdP) and FortiClient EMS is the service provider (SP). This feature allows users to log in to EMS by logging in with their AD FS credentials.

The following instructions assume that you have already installed and configured AD FS.

To configure SAML SSO with AD FS as IdP:
  1. In FortiClient EMS, go to Administration > SAML SSO. Service Provider Settings displays the SP Address, SP Entity ID, and SP ACS (login) URL fields. You use these values to configure FortiClient EMS as an SP in AD FS. Copy these values.
  2. Create and configure your FortiClient EMS environment in AD FS:
    1. Open AD FS Management and right-click Relying Party Trusts and select Add Relying Party Trust. This launches the Add Relying Party Trust Wizard. Select Claims Aware and click Next.
    2. In Select Data Source, select Enter data about the relying party manually and click Next.
    3. Enter a Display name and click Next.
    4. In Configure Certificate, leave the certificate settings at their default values. Click Next.
    5. In Configure URL, select Enable Support for the SAML 2.0 WebSSO protocol, then enter the SAML SSO URL obtained from EMS (SP ACS (login) URL).
    6. In Configure Identifiers, enter the Relying party trust identifier URL obtained from EMS (SP Entity ID), then click Add and Next.
    7. In Choose Access Control Policy, leave the default value (Permit everyone) and click Next.
    8. In Ready to Add Trust, review your settings, click Next.
    9. In Finish, select Configure claims issuance policy for this application, then click Close.
  3. Create claim rules:
    1. In the Issuance Transform Rules tab of the Claim Rules editor, click Add Rule.
    2. In Choose Rule Type, select Send LDAP Attributes as Claims from the dropdown list, then click Next.
    3. In Configure Claim Rule, enter a Claim Rule Name, select Active Directory as the Attribute Store, then add the following mapping: from the LDAP Attribute column, select SAM-Account-Name. In the Outgoing Claim Type column, enter Name ID, then click Finish to add the rule. Click OK.
  4. Export the IdP certificate, which you must later upload to EMS to finish SAML configuration:
    1. Open the AD FS management snap-in, select AD FS > Service > Certificates, then double-click the certificate under Token-signing. You can also right-click the field, then select View Certificate in the context menu.
    2. In Certificate, open the Details tab, then select Copy to File and click OK.
    3. In Certificate Export Wizard, click Next.
    4. Select Base-64 encoded X.509 (.CER), then click Next.
    5. In Certificate Export Wizard, select Browse to specify the location to export the IdP certificate to, then specify the file name and click Next.
    6. In Completing the Certificate Export Wizard, click Finish, then click OK to confirm the export succeeded.
  5. Configure the IdP information in FortiClient EMS:
    1. Export the metadata from AD FS by appending FederationMetadata/2007-06/FederationMetadata.xml to the AD FS server root URL. See the following example: https://adfs.domain.com/federationmetadata/2007-06/FederationMetadata.xml. The following shows an example on a local AD FS server: https://localhost/FederationMetadata/2007-06/FederationMetadata.xml.
    2. Obtain the IdP single sign-on URL and entity ID from the metadata. The following shows example values: IdP entity ID: http:/adfs.domain.com/adfs/services/trust IdP single sign-on URL: https:/adfs.domain.com/adfs/ls/
    3. In EMS, under Identity Provider Settings, paste the values obtained from the metadata in the IdP Entity ID and IdP single sign-on URL fields.
    4. Provide the certificate extracted in previous steps.
    5. (Optional) If desired, toggle on Enable Authorization Rules. When this feature is disabled, all SSO users from the IdP can become EMS admin users. When this feature is enabled, only SSO users from the IdP that satisfy a configured rule can become an EMS admin user. To add a rule, click Add. In the Authorization Rule field, enter a username. This field is case-insensitive. Add multiple rules as desired. Only SSO users from the IdP with usernames that match the configured authorization rules can access EMS as an admin user.
    6. Save the configuration.
Previous
Next