Example for Configuring Internet Access User Authentication

This section provides examples for configuring Internet access user authentication in different scenarios.

CLI: Example for Configuring Local Authentication on Internet Access Users (Portal Authentication): This section provides an example for configuring local authentication on Internet access users when a FW works as an egress gateway.

Web: Example for Configuring Local Authentication on Internet Access Users(Portal Authentication): This section provides an example for configuring local authentication on Internet access users when a FW works as an egress gateway.

CLI: Example for Configuring Authentication Exemption for Internet Access Users (Bidirectionally Binding Users to IP and MAC Addresses): This section describes how to configure authentication exemption for top executives and implement user-specific permission management when the FW serves as an egress gateway.

Web: Example for Configuring Authentication Exemption for Internet Access Users (Bidirectionally Binding Users to IP and MAC Addresses): This section describes how to configure authentication exemption for top executives and implement user-specific permission management when the FW serves as an egress gateway.

CLI: Example for Configuring AD SSO for Internet Access Users (Install ADSSO_Setup.exe to Receive Messages from PCs): This section provides an example for configuring AD Single Sign On (SSO) for Internet access users when a FW works as an egress gateway. In this example, the ADSSO_Setup.exe must be installed on the AD monitor (any computer in the AD domain, including the AD domain controller) and the login/logout scripts need to be set on the AD domain controller and delivered to PCs.

Web: Example for Configuring AD SSO for Internet Access Users (Install ADSSO_Setup.exe to receive messages from PCs): This section provides an example for configuring AD Single Sign On (SSO) for Internet access users when a FW works as an egress gateway. In this example, the ADSSO_Setup.exe must be installed on the AD monitor (any computer in the AD domain, including the AD domain controller) and the login/logout scripts need to be set on the AD domain controller and delivered to PCs.

CLI: Example for Configuring AD SSO for Internet Access Users (Multiple AD Servers + ADSSO_Setup.exe): This section provides an example for configuring AD Single Sign On (SSO) for Internet access users when a FW works as an egress gateway. In this example, the ADSSO_Setup.exe must be installed on the AD monitor (any computer in the AD domain, including the AD domain controller) and the login and logout scripts need to be set on the AD domain controller and delivered to PCs.

Web: Example for Configuring AD SSO for Internet Access Users (Multiple AD Servers + ADSSO_Setup.exe): This section provides an example for configuring AD SSO for Internet access users. When the FW serves as the egress gateway of an enterprise intranet, users can pass the authentication on the FW by logging in to the AD domain. In this example, ADSSO_Setup.exe needs to be installed on an AD monitor (any computer in the AD domain, including the AD domain controller), and the login and logout scripts need to be deployed on the AD controller and delivered to PCs.

CLI: Example for Configuring AD SSO for Internet Access Users (Install ADSSO_Setup.exe to query AD server security logs): This section provides an example for configuring AD Single Sign On (SSO) for Internet access users when a FW works as an egress gateway. In this example, the ADSSO_Setup.exe must be installed on the AD monitor (any computer in the AD domain, including the AD domain controller) to query AD server security logs in order to obtain the user login message.

Web: Example for Configuring AD SSO for Internet Access Users (Install ADSSO_Setup.exe to query AD server security logs): This section provides an example for configuring AD Single Sign On (SSO) for Internet access users when a FW works as an egress gateway. In this example, the ADSSO_Setup.exe must be installed on the AD monitor (any computer in the AD domain, including the AD domain controller) to query AD server security logs in order to obtain the user login message.

CLI: Example for Configuring AD SSO for Internet Access Users (the FW Monitoring AD Authentication Packets): This section provides an example for configuring AD Single Sign On (SSO) for Internet access users when a FW works as an egress gateway. In this example, no additional program is required. The FW obtains user login information from AD authentication packets.

Web: Example for Configuring AD SSO for Internet Access Users (the FW Monitoring AD Authentication Packets): This section provides an example for configuring AD Single Sign On (SSO) for Internet access users when a FW works as an egress gateway. In this example, no additional program is required. The FW obtains user login information from AD authentication packets.

CLI: Example for Configuring Agile Controller SSO for Internet Access Users (Users Proactively Access the Controller): This section provides an example for configuring Agile Controller (Policy Center or Agile Controller) Single Sign On (SSO) for Internet access users when a FW works as an egress gateway. Users need to proactively access the Agile Controller portal authentication page and must be authenticated before accessing services.

Web: Example for Configuring Agile Controller SSO for Internet Access Users (Users Proactively Access the Controller): This section provides an example for configuring Agile Controller (Policy Center or Agile Controller) Single Sign On (SSO) for Internet access users when a FW works as an egress gateway. Users need to proactively access the Agile Controller portal authentication page and must be authenticated before accessing services.

CLI: Example for Configuring Agile Controller SSO for Internet Access Users (Users' HTTP Services Are Redirected to the Controller): This section provides an example for configuring Agile Controller (Policy Center or Agile Controller) Single Sign On (SSO) for Internet access users when a FW works as an egress gateway. In redirected authentication, users access HTTP services, and the FW then redirects the HTTP requests to the Agile Controller portal authentication page. After the authentication succeeds, the users continue to access services.

Web: Example for Configuring Agile Controller SSO for Internet Access Users (Users' HTTP Services Are Redirected to the Controller): This section provides an example for configuring Agile Controller (Policy Center or Agile Controller) Single Sign On (SSO) for Internet access users when a FW works as an egress gateway. In redirected authentication, users access HTTP services, and the FW then redirects the HTTP requests to the Agile Controller portal authentication page. After the authentication succeeds, the users continue to access services.

CLI: Example for Configuring Portal Authentication for Internet Access Users (the FW Participates in User Authentication): This section provides an example for configuring the FW that serves as an egress gateway to complete user authentication with the Agile Controller. Users can directly access HTTP services. The FW redirects HTTP requests to the Portal authentication page of the Agile Controller. The Agile Controller sends authentication requests to the FW. The user can access desired services after the authentication succeeds.

Web: Example for Configuring Portal Authentication for Internet Access Users (the FW Participates in User Authentication): This section provides an example for configuring the FW that serves as an egress gateway to complete user authentication with the Agile Controller. Users can directly access HTTP services. The FW redirects HTTP requests to the Portal authentication page of the Agile Controller. The Agile Controller sends authentication requests to the FW. The user can access desired services after the authentication succeeds.

CLI: Example for Configuring Portal Authentication for Internet Access Users (the FW Participates in User Authentication+MAC Address-Prioritized Portal Authentication): This section provides an example of configuring the FW that serves as the enterprise egress gateway to work with the Agile Controller for portal authentication and MAC authentication on users.

Web Example: Internet Access User + Agile Controller as a Portal Server (the FW Participates in User Authentication) + MAC Address-prioritized Portal Authentication: This example describes how to configure the FW that serves as the egress gateway of an enterprise to work with the Agile Controller to perform portal authentication and MAC address-prioritized portal authentication on users.

CLI: Example for Configuring RADIUS SSO for Internet Access Users: This section provides an example for configuring RADIUS Single Sign On (SSO) for Internet access users when a FW works as an egress gateway.

Web: Example for Configuring RADIUS SSO for Internet Access Users: This section provides an example for configuring RADIUS Single Sign On (SSO) for Internet access users when a FW works as an egress gateway.

CLI: Example for Configuring RADIUS SSO for Internet Access Users (RADIUS Attribute as a Security Group): In this example, the FW serves as the egress gateway of an enterprise. Users who pass the authentication of the RADIUS authentication system directly pass the FW's authentication. The FW can parse RADIUS attributes and use the parsed attribute as the security group.

Web: Example for Configuring RADIUS SSO for Internet Access Users (RADIUS Attribute as a Security Group): In this example, the FW serves as the egress gateway of an enterprise. Users who pass the authentication of the RADIUS authentication system directly pass the FW's authentication. The FW can parse RADIUS attributes and use the parsed attribute as the security group.

CLI: Example for Configuring RADIUS SSO for Internet Access Users (Out-of-Path Mode): This section provides an example for configuring RADIUS Single Sign On (SSO) for Internet access users when a FW works as an egress gateway.

Web: Example for Configuring RADIUS SSO for Internet Access Users (Out-of-Path Mode): This section provides an example for configuring RADIUS Single Sign On (SSO) for Internet access users when a FW works as an egress gateway.

CLI: Example for Configuring RADIUS Server Authentication on Internet Access Users: This section provides an example for configuring RADIUS server authentication on Internet access users when a FW works as an egress gateway.

Web: Example for Configuring RADIUS Server Authentication on Internet Access Users: This section provides an example for configuring RADIUS server authentication on Internet access users when a FW works as an egress gateway.

CLI: Example for Configuring LDAP Server Authentication on Internet Access Users: This section provides an example for configuring a Sun ONE LDAP server to implement authentication on Internet access users when a FW works as an egress gateway.

Web: Example for Configuring LDAP Server Authentication on Internet Access Users: This section provides an example for configuring a Sun ONE LDAP server to implement authentication on Internet access users when a FW works as an egress gateway.

CLI: Example for Configuring Agile Controller SSO Authenticating and AD Server Import for Internet Access Users: In this example, the FW serves as the egress gateway of an enterprise network; a Agile Controller server (Policy Center or Agile Controller) is used to authenticate users; user permission is controlled based on the organizational structure on an AD server.

Web: Example for Configuring Agile Controller SSO Authenticating and AD Server Import for Internet Access Users: In this example, the FW serves as the egress gateway of an enterprise network; a Agile Controller server (Policy Center or Agile Controller) is used to authenticate users; user permission is controlled based on the organizational structure on an AD server.

CLI: Example for Configuring WeChat Authentication on Internet Access Users

Web: Example for Configuring WeChat Authentication on Internet Access Users

CLI: Example for Configuring NTLM Authentication for Internet Access Users: This section describes an example that no authentication is required when the user logs in to the AD domain and accesses the Internet through the browser in a scenario where the FW serves as the enterprise egress gateway. The FW obtains the user identity through NTLM authentication.

Web: Example for Configuring NTLM Authentication for Internet Access Users: This section describes an example that no authentication is required when the user logs in to the AD domain and accesses the Internet through the browser in a scenario where the FW serves as the enterprise egress gateway. The FW obtains the user identity through NTLM authentication.

Web: Example for Online Querying and Referencing the Specified Users/User Groups on the AD Server Using Security Policies

CLI: Example for Implementing Permission Control on Users Who Access the Internet Through an HTTP Proxy Server: This section provides an example for implementing permission control on users who access the Internet through an HTTP proxy server. When a user sends a packet to access the Internet through an HTTP proxy server, the FW parses the X-Forwarded-For field in the HTTP packet to obtain the user identity and controls the permission of the user.

Web: Example for Implementing Permission Control on Users Who Access the Internet Through an HTTP Proxy Server: This section provides an example for implementing permission control on users who access the Internet through an HTTP proxy server. When a user sends a packet to access the Internet through an HTTP proxy server, the FW parses the X-Forwarded-For field in the HTTP packet to obtain the user identity and controls the permission of the user.