Fortinet SSO Configuration and Setup Guide

Author

Reads 384

Close-up of a surveillance camera with neon lighting, symbolizing modern home security technology.
Credit: pexels.com, Close-up of a surveillance camera with neon lighting, symbolizing modern home security technology.

To configure Fortinet SSO, you'll need to start by enabling the SAML feature in the Fortinet device's settings. This allows the device to accept SAML authentication requests from your identity provider.

The Fortinet device will then generate an XML file containing its SAML metadata, which you'll need to upload to your identity provider's console. This file contains the device's identity provider details.

Once uploaded, you can configure the identity provider to send authentication requests to the Fortinet device. The Fortinet device will then authenticate the user and send an authentication response back to the identity provider.

The Fortinet device supports several identity providers, including Active Directory and OpenLDAP. You can choose the one that best fits your organization's needs.

If this caught your attention, see: Azure Ad Sso Saml Example

Configuring the FortiAuthenticator

To configure the FortiAuthenticator, start by going to Fortinet SSO Methods > SSO > General. The default listening port is 8000, but you can change it if your network requires a different setting.

Credit: youtube.com, FortiAuthenticator SAML SSO

The FortiAuthenticator unit can be integrated with external network authentication systems, such as RADIUS, LDAP, Windows AD, and FortiClients. To do this, you'll need to select Enable authentication and enter the Secret key.

In the Fortinet Single Sign-On (FSSO) section, you'll need to enter the following information:

Make sure to use the same secret key when configuring the FSSO Agent on FortiGate units.

User Authentication

User authentication is a crucial aspect of Fortinet SSO. To configure user authentication settings, go to User & Authentication > Authentication Settings and set the Certificate to a custom certificate that the user trusts.

The custom certificate's SAN field should have the FQDN or IP address from the SP URL. Alternatively, assigning a CA certificate allows the FortiGate to automatically generate and sign a certificate for the authentication daemon.

You can also use Duo Authentication, which redirects users to Duo for two-factor authentication before allowing them to log in to Fortinet FortiGate. To set up Duo, link to Fortinet FortiGate in Duo Central and add it as an application tile.

Credit: youtube.com, 12- What is Fortinet Single Sign-On (FSSO) + How to Set it Up ?

FortiAuthenticator can be integrated with external network authentication systems, such as RADIUS, LDAP, Windows AD, and FortiClients. To configure FortiAuthenticator, go to Fortinet SSO Methods > SSO > General and select Enable authentication, entering the Secret key.

The FortiGate unit needs to be added to the FortiAuthenticator as an SSO agent that will provide user logon information. To do this, go to Security Fabric > Fabric Connectors and select Create New, then select Fortinet Single-Sign-On Agent.

Here is a list of steps to configure the FortiGate:

  1. Go to Security Fabric > Fabric Connectors and select Create New.
  2. Under SSO/Identity, select Fortinet Single-Sign-On Agent.
  3. Enter a Name, set Primary FSSO Agent either to the IP address of the FortiAuthenticator unit or a name, and enter a Password.
  4. Set Collector Agent AD access mode to either Standard, where you can specify Users/Groups, or Advanced, where you can specify an LDAP Server.
  5. Select OK.

Note that the CLI configurations for SSO apply to all versions of FortiOS and are shown below:

SAML Settings

To set up SAML for Fortinet SSO, you'll need to upload the Base64-encoded SAML certificate to your FortiGate appliance. Simply sign in to the management portal, select System, then Certificates, and import the certificate from the FortiGate app deployment in your Azure tenant.

The SAML login experience depends on your Duo SSO routing rules configuration. With a single SAML identity provider enabled and the default routing rule in place, users will be immediately redirected to that provider for primary authentication.

Credit: youtube.com, Azure SAML Authentication with FortiGate Firewall for SSL VPN: Step-by-Step Guide

To configure the Fortinet FortiGate Administrators application in Duo, log in to the Duo Admin Panel and navigate to Applications > Application Catalog. Locate the entry for Fortinet FortiGate Administrators with the "SSO" label and click the + Add button to start configuring.

The application uses the Mail attribute and Username attribute when authenticating, and these attributes are mapped to external authentication source attributes as follows:

Be sure to update the User access setting to grant access to this application to users in selected Duo groups, or to all users.

Common SAML Settings

When uploading the Base64 SAML Certificate to the FortiGate appliance, you need to sign in to the management portal of your FortiGate appliance.

To access the System menu, select System in the left pane.

Under System, select Certificates.

To import the certificate, select Import > Remote Certificate.

The certificate downloaded from the FortiGate app deployment in the Azure tenant should be selected and then OK should be chosen.

Credit: youtube.com, How to Connect a SAML App in PingFederate & View Assertion Details in the SAML Response

After the certificate is uploaded, take note of its name under System > Certificates > Remote Certificate.

By default, the certificate is named REMOTE_Cert_N, where N is an integer value.

Here's a quick reference of the steps to upload the certificate:

  1. Sign in to the management portal of your FortiGate appliance.
  2. Under System, select Certificates.
  3. Select Import > Remote Certificate.
  4. Browse to the certificate downloaded from the FortiGate app deployment in the Azure tenant, select it, and then select OK.

SAML Login

The SAML login experience is quite interesting, and it's all about how you've configured your Duo SSO routing rules. If you have a default routing rule in place and only one SAML identity provider enabled, users will be immediately redirected to that SAML IdP for primary authentication.

Users won't even see the Duo SSO primary login screen. This is because the default routing rule takes priority, and it's directing the login attempt to the SAML IdP.

However, if you have multiple SAML authentication sources enabled or custom routing rules set up, things get a bit more complicated. In this case, users will enter their primary username (email address) on the Duo SSO login page, and then they'll be redirected to the correct external SAML identity provider.

This is where the routing rules come into play, and it's essential to configure them correctly to ensure a smooth login experience for your users.

If this caught your attention, see: Store Login Session Nextjs

Authentication

Credit: youtube.com, FortiGate Admin Login with SAML SSO | Entra ID

Authentication is handled by the FortiGate, which listens on port 1003 for incoming requests when traffic matches an identity-based firewall policy.

The FortiGate uses a local server certificate to secure connections, which must be trusted by the client making the authentication request. This can be avoided by using a custom certificate that the user trusts.

To use a custom certificate, go to User & Authentication > Authentication Settings and set Certificate to the custom certificate. If the certificate is not available, click Create to create or import a new custom certificate.

Alternatively, you can assign a CA certificate to the FortiGate, which will automatically generate and sign a certificate for the authentication daemon. This will override any assigned server certificate.

Successful verification of primary credentials by Active Directory or a SAML IdP redirects back to Duo for two-factor authentication.

Authentication Port

The authentication port is a crucial setting for FortiGate devices, and it's used to listen for incoming authentication requests. By default, it listens on port 1003.

Credit: youtube.com, 802.1X | Network Basics

This setting is particularly important for SAML SPs, as it allows the FortiGate to redirect SAML authentication requests to the IdP. In other words, it's a key part of the authentication process.

If you have an identity based firewall policy configured for your SAML user group, the FortiGate will use the same port to listen for SAML authentication requests. This ensures a seamless authentication experience for your users.

Authentication

Authentication is a crucial aspect of securing your FortiGate. By default, the FortiGate listens on port 1003 for incoming authentication requests when traffic matches an identity-based firewall policy.

To avoid certificate warnings, you can use a custom certificate that the user trusts. This involves setting the Certificate to the custom certificate in the User & Authentication > Authentication Settings.

The authentication daemon uses a local server certificate to secure the connection. If the client doesn't trust the certificate, they'll receive a certificate warning.

Credit: youtube.com, Web Authentication Methods Explained

To assign a CA certificate, edit the user setting and set auth-ca-cert to the CA certificate name. This will allow the FortiGate to automatically generate and sign a certificate for the authentication daemon.

Here are the steps to assign a CA certificate:

Successful verification of your primary credentials by Active Directory or a SAML IdP redirects back to Duo for two-factor authentication. This applies to both users and administrators.

You can also log into Fortinet FortiGate using Duo Central, our cloud-hosted portal, which allows users to access all their applications in one spot. Link to Fortinet FortiGate in Duo Central by adding it as an application tile.

A different take: Duo Security Sso

Test

To test your Fortinet SSO configuration, you need to follow these steps.

First, you'll need to configure Microsoft Entra SSO to enable the feature for your users. This involves establishing a link relationship between a Microsoft Entra user and the corresponding SAML SSO user group in FortiGate SSL VPN.

Credit: youtube.com, FortiGate Firewall: Why use Fortinet Single Sign On (FSSO)? What are the benefits!

To verify that the configuration works, you can test SSO by redirecting to FortiGate VPN Sign-on URL.

You can initiate the sign-in flow from FortiGate VPN Sign-on URL directly.

Alternatively, you can use Microsoft My Apps to test SSO. When you select the FortiGate VPN tile in the My Apps, it will redirect to FortiGate VPN Sign-on URL.

Here are the specific options you can use to test SSO:

  • In Step 5) of the Azure SSO configuration, select the Test button to redirect to FortiGate VPN Sign-on URL.
  • Go to FortiGate VPN Sign-on URL directly and initiate the sign-in flow from there.
  • Use Microsoft My Apps and select the FortiGate VPN tile to redirect to FortiGate VPN Sign-on URL.

SSL VPN and FortiClient

SSL VPN and FortiClient is a powerful combination for secure remote access. FortiClient 6.4.0 and later support SAML authentication for SSL VPN.

If you're using FortiClient, you can configure it to work with Duo SSO authentication. To do this, select the VPN tunnel configured for Duo SSO authentication on the FortiClient application's "Remote Access" tab.

To log in, click SAML Login and you'll be prompted to log in to Duo SSO. Complete Duo two-factor authentication to connect.

You might enjoy: Fortinet Vpn down

Single Sign-On

Single Sign-On is a feature that allows users to access multiple applications with a single set of login credentials. You can configure Fortinet FortiGate for SSO using Security Assertion Markup Language (SAML) 2.0 authentication.

Credit: youtube.com, Fortinet: How to Setup Single Sign On on your FortiGate Firewall

To get started, you'll need to configure a working authentication source, such as Active Directory or another SSO IdP. Once you have that set up, you can create the Fortinet FortiGate application in Duo, which will prompt users for two-factor authentication and perform endpoint assessment and verification before permitting access.

You can also use FortiAuthenticator SSO user groups directly in identity-based security policies, but you'll need to create an FSSO user group and add FortiAuthenticator SSO user groups to it. The groups available to add as members are SSO groups provided by SSO agents.

Here are the steps to create the Fortinet FortiGate application in Duo:

  1. Log in to the Duo Admin Panel and navigate to Applications → Application Catalog.
  2. Locate the entry for Fortinet FortiGate with the "SSO" label in the catalog and click the + Add button.
  3. No active Duo users can log in to new applications until you grant access.

You can also create the Fortinet FortiGate Administrators application in Duo, which will use the Mail attribute and Username attribute when authenticating. Fortinet FortiGate Administrators uses the same attributes as Fortinet FortiGate, but you'll need to follow the same steps to create the application in Duo.

Group Matching

Credit: youtube.com, WEBINAR: Single sign-on (SSO) security feature

To configure group matching, you need to establish an SSH session to your FortiGate appliance and sign in with a FortiGate Administrator account. This will allow you to run specific commands to configure group matching.

You'll need to run the command `config user group` to edit the FortiGateAccess user group, and then set the member to azure. Next, you'll need to configure the match settings by editing the server-name to azure and the group-name to the Object ID of the FortiGateAccess security group.

Here's a step-by-step guide to configuring group matching:

1. Establish an SSH session to your FortiGate appliance and sign in with a FortiGate Administrator account.

2. Run the command `config user group` to edit the FortiGateAccess user group.

3. Set the member to azure.

4. Configure the match settings by editing the server-name to azure and the group-name to the Object ID of the FortiGateAccess security group.

By following these steps, you'll be able to configure group matching and allow FortiGate to make access decisions based on group membership.

Recommended read: Caller ID

Single Sign-On

Credit: youtube.com, What is Single Sign-On (SSO)? - Beginner’s Cybersecurity Series

Single Sign-On is a feature that allows users to access multiple applications with a single set of credentials. This can be achieved through a cloud-hosted SSO product like Duo Single Sign-On, which layers strong authentication and a flexible policy engine on top of Fortinet FortiGate logins.

To configure Single Sign-On, you'll first need to configure a working authentication source, such as Active Directory or another SSO IdP. Once you have a working authentication source, you can create the Fortinet FortiGate application in Duo.

Duo Single Sign-On is available in various plans, including Duo Premier, Duo Advantage, and Duo Essentials. These plans also include the ability to define policies that enforce unique controls for each individual SSO application.

You can require that users complete two-factor authentication at every login, but only once every seven days when accessing certain applications. Duo checks the user, device, and network against an application's policy before allowing access to the application.

Credit: youtube.com, What Is Single Sign-on (SSO)? How It Works

To test Single Sign-On, you can use a test user like B.Simon and configure Microsoft Entra SSO with FortiGate SSL VPN. You can initiate the sign-in flow from the FortiGate VPN Sign-on URL or use Microsoft My Apps to redirect to the FortiGate VPN Sign-on URL.

In SAML authentication, the server certificate used by the authentication daemon must be trusted by the user. You can use a custom certificate that the user trusts or assign a CA certificate to automatically generate and sign a certificate for the authentication daemon.

Here are some common claims required by FortiGate SSL VPN:

Note that user attributes & claims allow only one group claim, so you'll need to delete the existing group claim or edit the existing one to add the new claim.

Consider reading: Anti-Spam Research Group

Prerequisites and Setup

To get started with FortiGate SSO, you'll need a few essential items. A Microsoft Entra subscription is required, and the good news is that you can get a free account if you don't already have one.

To enable single sign-on on your FortiGate SSL VPN, make sure it's enabled.

Here are the specific items you'll need to get started:

  • A Microsoft Entra subscription
  • A FortiGate SSL VPN with single sign-on (SSO) enabled

CLI and Configuration

Credit: youtube.com, #Fortinet | How to Configure FSSO | Passive Authentication | Part 2 | DAY 25 | NSE4 Training

The CLI syntax for FSSO is straightforward, with commands to set the server address, port, and password for multiple FSSO agents. You can use the `edit` command to set the server address, port, and password for each agent.

To set the Active Directory server port, you can use the `set port` command. This command is particularly useful when configuring FSSO with Active Directory.

For a more comprehensive CLI configuration, you can refer to the section on "Complete FortiGate command-line configuration". This section provides a table mapping FortiGate SAML CLI settings to their equivalent Azure configurations.

Configuring the Mobility Agent

Configuring the Mobility Agent is a straightforward process. You'll need to know the FortiAuthenticator IP address and pre-shared key/secret.

To start, go to FortiClient and click on File > Settings. Under Advanced, select Enable Single Sign-On mobility agent.

Next, enter the IP address of the FortiAuthenticator in the Server address field. You can omit the port number if it's 8005, but if it's different, enter it in the Customize port field.

The pre-shared key is also crucial, so make sure to enter it correctly. Once you've entered all the necessary information, click OK to save your changes.

For more detailed FSSO configurations, refer to the FortiOS Administration Guide.

For your interest: Message Submission Agent

Test Microsoft Entra

Credit: youtube.com, Setting up SAML SSO with Azure Entra ID and Fortigate SSLVPN

To test Microsoft Entra SSO, you'll need to follow these steps. First, test single sign-on with your App by selecting the Test button in Step 5 of the Azure SSO configuration. This option redirects to the FortiGate VPN Sign-on URL, where you can initiate the sign-in flow.

The FortiGate VPN Sign-on URL can also be accessed directly, allowing you to initiate the sign-in flow from there. To do this, simply go to the FortiGate VPN Sign-on URL and follow the prompts.

Another way to test Microsoft Entra SSO is by using Microsoft My Apps. When you select the FortiGate VPN tile in My Apps, it redirects to the FortiGate VPN Sign-on URL.

Here are the three options for testing Microsoft Entra SSO:

  • Test single sign-on with your App
  • Go to FortiGate VPN Sign-on URL directly
  • Use Microsoft My Apps

Each of these options provides a different way to test your Microsoft Entra SSO configuration. By trying out each one, you can ensure that your SSO setup is working correctly.

Leslie Larkin

Senior Writer

Leslie Larkin is a seasoned writer with a passion for crafting engaging content that informs and inspires her audience. With a keen eye for detail and a knack for storytelling, she has established herself as a trusted voice in the digital marketing space. Her expertise has been featured in various articles, including "Virginia Digital Marketing Experts," a series that showcases the latest trends and strategies in online marketing.

Love What You Read? Stay Updated!

Join our community for insights, tips, and more.