Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY 2.4.3
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
All Products
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Web Application 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
  • Web Application / API Protection
  • 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
    • All Products

    Release Notes

    Home FortiGuest 2.4.3 Release Notes
    2.4.3
    2.4.3
    2.4.2
    2.4.1
    2.4.0
    2.2.1
    2.2.0
    2.0.0
    1.3.1
    1.3.0
    1.2.2
    1.2.1
    1.2.0
    1.1.0
    1.0.0

    About this Release

    About this Release

    This release delivers key new features and few bug fixes. For more information, see What's New and Resolved Issues sections.

    Notes:

    • Multi Pre Shared Key (MPSK): When an MPSK device is created, it gets its own Device Account Group (mapped under Guest Portal Access Plan). When the device actually connects, the authorization policy/profile decision is not based on the Device Account Group. Instead, it uses the User Account Group (to which the MPSK is mapped or bound).

    • CLI/GUI passwords:

      • After an upgrade, the CLI password remains the same until a user logs in using the GUI. Once the first successful GUI login occurs, the CLI password is automatically synchronized and set to match the GUI password.

      • On the first bootup of a new instance, a user must first log in using the CLI and change the default password. Once the CLI password is updated, it will also be used for logging into the GUI.

    • Only one of the four port interfaces can support DHCP configuration at a time.

    Previous
    Next

    About this Release

    About this Release

    This release delivers key new features and few bug fixes. For more information, see What's New and Resolved Issues sections.

    Notes:

    • Multi Pre Shared Key (MPSK): When an MPSK device is created, it gets its own Device Account Group (mapped under Guest Portal Access Plan). When the device actually connects, the authorization policy/profile decision is not based on the Device Account Group. Instead, it uses the User Account Group (to which the MPSK is mapped or bound).

    • CLI/GUI passwords:

      • After an upgrade, the CLI password remains the same until a user logs in using the GUI. Once the first successful GUI login occurs, the CLI password is automatically synchronized and set to match the GUI password.

      • On the first bootup of a new instance, a user must first log in using the CLI and change the default password. Once the CLI password is updated, it will also be used for logging into the GUI.

    • Only one of the four port interfaces can support DHCP configuration at a time.

    Previous
    Next