Fortinet Fortinet 1.5 Technical Note Download Page 5

Using FSAE on your network 

FSAE overview

Fortinet Server Authentication Extension Version 1.5 Technical Note
01-30005-0373-20071001

5

Using FSAE on your network

The Fortinet Server Authentication Extension (FSAE) provides seamless 
authentication of Microsoft Windows Active Directory users on FortiGate units. 
This chapter describes how to install and configure FSAE on your Microsoft 
Windows network and how to configure your FortiGate unit to authenticate users 
using FSAE. 

The following topics are included in this chapter:

FSAE overview

Installing FSAE on your network

Configuring FSAE on Windows AD

Configuring FSAE on FortiGate units

Testing the configuration

NTLM authentication

FSAE overview

On a Microsoft Windows network, users authenticate at logon. It would be 
inconvenient if users then had to enter another user name and password for 
network access through the FortiGate unit. FSAE provides authentication 
information to the FortiGate unit so that users automatically get access to 
permitted resources.

FortiGate units control access to resources based on user groups. Through 
FSAE, the Windows Active Directory (AD) groups are known to the FortiGate unit 
and you can include them as members of FortiGate user groups.

There are two mechanisms for passing user authentication information to the 
FortiGate unit:

FSAE software installed on a domain controller monitors user logons and 
sends the required information directly to the FortiGate unit

using the NTLM protocol, the FortiGate unit requests information from the 
Windows network to verify user authentication. This is used where it is not 
possible to install FSAE on the domain controller. The user must use the 
Internet Explorer (IE) browser.

FSAE has two components that you must install on your network:

The domain controller (DC) agent must be installed on every domain controller 
to monitor user logons and send information about them to the collector agent.

The collector agent must be installed on at least one domain controller to send 
the information received from the DC agents to the FortiGate unit.

Summary of Contents for Fortinet 1.5

Page 1: ...www fortinet com Fortinet Server Authentication Extension Version 1 5 T E C H N I C A L N O T E...

Page 2: ...Trademarks Dynamic Threat Prevention System DTPS APSecure FortiASIC FortiBIOS FortiBridge FortiClient FortiGate FortiGate Unified Threat Management System FortiGuard FortiGuard Antispam FortiGuard Ant...

Page 3: ...Ignore List 11 Configuring FortiGate group filters 11 To view the FortiGate Filter List 12 To configure a FortiGate group filter 12 Configuring TCP ports 13 Configuring FSAE on FortiGate units 14 Spe...

Page 4: ...Fortinet Server Authentication Extension Version 1 5 Technical Note 4 01 30005 0373 20071001 Contents...

Page 5: ...the FortiGate unit so that users automatically get access to permitted resources FortiGate units control access to resources based on user groups Through FSAE the Windows Active Directory AD groups ar...

Page 6: ...t by the FSAE agent on the domain controller and if authentication is successful the information is then sent via the collector agent to the FortiGate unit Figure 2 NTLM FSAE implementation In Figure...

Page 7: ...tor privileges and a password that does not expire Installing FSAE To install FSAE you must obtain the FortiClient Setup file from the Fortinet Support web site Perform the following installation proc...

Page 8: ...e able to authenticate to FortiGate units using FSAE You can also do this later See Configuring FSAE on Windows AD on page 8 15 Select Next 16 Optionally clear the check boxes of domain controllers on...

Page 9: ...Professional Configuring Windows AD server user groups FortiGate units control access at the group level All members of a group have the same network access as defined in FortiGate firewall policies Y...

Page 10: ...st Exclude users such as system accounts that do not authenticate to any FortiGate unit See Configuring the Global Ignore List on page 11 FortiGate Group Filter Configure group filtering for each Fort...

Page 11: ...nada Timers Workstation verify interval Enter the interval in minutes at which FSAE checks whether the user is still logged in The default is every 5 minutes If ports 139 or 445 cannot be opened on yo...

Page 12: ...te If no filter is defined for a FortiGate unit and there is no default filter the collector agent sends all Windows AD group and user logon events to the FortiGate unit While this normally is not a p...

Page 13: ...rs on page 11 in the Configuring collector agent settings section Default Select to create the default filter The default filter applies to any FortiGate unit that does not have a specific filter defi...

Page 14: ...sses these servers in the order that they appear in the list If a server becomes unavailable the unit accesses the next one in the list To specify collector agents 1 Go to User Windows AD and select C...

Page 15: ...hould be belong to only one FortiGate user group If you assign it to multiple FortiGate user groups the FortiGate unit recognizes only the last user group assignment To create a user group for FSAE au...

Page 16: ...ting firewall policies Policies that require FSAE authentication are very similar to other firewall policies Currently only one single authentication firewall policy can be configured if the source in...

Page 17: ...ortiGate unit 2 Try to connect to the resource that is protected by the firewall policy requiring authentication via FSAE You should be able to connect to the resource without being asked for username...

Page 18: ...oded with the client password it may contain the challenge nonce twice using different algorithms 6 The FortiGate unit checks with the FSAE client over port 8000 to see if the authentication hash matc...

Page 19: ...www fortinet com...

Page 20: ...www fortinet com...

Reviews: