Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • Administration Guide

    Home FortiAuthenticator 6.0.1 Administration Guide
    6.0.1
    6.6.2
    6.6.1
    6.6.0
    6.5.5
    6.5.4
    6.5.3
    6.5.2
    6.5.1
    6.5.0
    6.4.10
    6.4.9
    6.4.8
    6.4.7
    6.4.6
    6.4.5
    6.4.4
    6.4.3
    6.4.2
    6.4.1
    6.4.0
    6.3.4
    6.3.3
    6.3.2
    6.3.1
    6.3.0
    6.2.2
    6.2.1
    6.2.0
    6.1.3
    6.1.2
    6.1.1
    6.1.0
    6.0.8
    6.0.7
    6.0.6
    6.0.5
    6.0.4
    6.0.3
    6.0.2
    6.0.1
    6.0.0
    5.5.0
    5.4.0
    5.3.0
    5.2.0
    5.1.0
    5.0.0
    4.3.0
    4.2.1
    4.2.0

    What's new in FortiAuthenticator 6.0.1

    What's new in FortiAuthenticator 6.0.1

    The following list contains new and expanded features added in FortiAuthenticator 6.0.1.

    Support for FortiToken Cloud

    FortiAuthenticator adds support for token-based authentication through the FortiToken Cloud service. This service offers centralized and simplified management of two-factor tokens. You will be able to use this feature when the FortiToken Cloud service provides support for FortiAuthenticator.

    Guest portals: Automatic login after registration

    When configuring a guest portal, you have the option to automatically log new users into the guest network after they successfully register.

    Client certificate for TLS authentication with remote LDAP servers

    FortiAuthenticator can be configured to communicate with a remote LDAP server over TLS, using a client certificate to authenticate the TLS connection. This is useful in cases where you want to connect FortiAuthenticator as an LDAP client to secure LDAP services, such as the one offered by G Suite.

    SAML IdP enhancements

    The SAML IdP feature includes a few customization enhancements. You can:

    • use different IdP-signing certificates for each Service Provider (SP). This can be useful when renewing a certificate before expiry, allowing staged updates of the various SPs.
    • specify up to three alternative ACS login URLs for each SP.
    • customize the replacement message for the SAML IdP Request Expired page. This page appears when the SP request expires due to the end-user waiting too long on the SAML IdP login page before proceeding with the login.

    Node-specific default gateway

    You can now define a node-specific default gateway for the FortiAuthenticator device if it differs from the default gateway of the other HA cluster member. To add the default gateway go so System > Administration > High Availability or use the following CLI command:

    configure system ha

    set ns-gw <gateway>

    More granular control for purging disabled user accounts

    When configuring the general user account policy settings, you have the option to automatically purge disabled user accounts on an hourly basis.

    REST API enhancement: OAuth verify token returns username

    The /oauth/verify_token/ endpoint now returns the username associated to the valid OAuth token.

    Previous
    Next

    What's new in FortiAuthenticator 6.0.1

    What's new in FortiAuthenticator 6.0.1

    The following list contains new and expanded features added in FortiAuthenticator 6.0.1.

    Support for FortiToken Cloud

    FortiAuthenticator adds support for token-based authentication through the FortiToken Cloud service. This service offers centralized and simplified management of two-factor tokens. You will be able to use this feature when the FortiToken Cloud service provides support for FortiAuthenticator.

    Guest portals: Automatic login after registration

    When configuring a guest portal, you have the option to automatically log new users into the guest network after they successfully register.

    Client certificate for TLS authentication with remote LDAP servers

    FortiAuthenticator can be configured to communicate with a remote LDAP server over TLS, using a client certificate to authenticate the TLS connection. This is useful in cases where you want to connect FortiAuthenticator as an LDAP client to secure LDAP services, such as the one offered by G Suite.

    SAML IdP enhancements

    The SAML IdP feature includes a few customization enhancements. You can:

    • use different IdP-signing certificates for each Service Provider (SP). This can be useful when renewing a certificate before expiry, allowing staged updates of the various SPs.
    • specify up to three alternative ACS login URLs for each SP.
    • customize the replacement message for the SAML IdP Request Expired page. This page appears when the SP request expires due to the end-user waiting too long on the SAML IdP login page before proceeding with the login.

    Node-specific default gateway

    You can now define a node-specific default gateway for the FortiAuthenticator device if it differs from the default gateway of the other HA cluster member. To add the default gateway go so System > Administration > High Availability or use the following CLI command:

    configure system ha

    set ns-gw <gateway>

    More granular control for purging disabled user accounts

    When configuring the general user account policy settings, you have the option to automatically purge disabled user accounts on an hourly basis.

    REST API enhancement: OAuth verify token returns username

    The /oauth/verify_token/ endpoint now returns the username associated to the valid OAuth token.

    Previous
    Next