This section describes the basic configurations of SACG.
This function is successfully enabled only if the Agile Controller server is correctly configured.
This function checks the status of the connection between the device and the Agile Controller server.
The status detection determines whether the number of connected Agile Controller servers is smaller than the minimum number of active servers. If yes, open the emergency channel to allocate all permissions to users; otherwise, disable the emergency channel to restore to original permissions.
The Minimum Number of Active Servers option takes effect only after the function is enabled.
It indicates the minimum number of the Agile Controller servers connecting to the device.
When the status detection function is enabled and the number of connected Agile Controller servers is smaller than the value, the device enables the emergency channel; otherwise, the device disables it.
This option takes effect only after the status detection function is enabled.
This function can check the number of active third-party servers.
In SACG scenarios, some account and password information is stored on the Agile Controller server, and some account and password information is stored on the third-party authentication server. When a user enters the account and password on the client to initiate an identity authentication request, if the account and password are stored on the Agile Controller server, the Agile Controller server authenticates the user. If the account and password are stored on the third-party authentication server, the AC-Campus will send the account information to the third-party server for authentication. The third-party server sends the authentication result to the AC-Campus. The AC-Campus authorizes the user based on the authentication result.
In the scenario where user authentication is done on the Agile Controller server, if the Service Controller detects that the number of active Agile Controller server is smaller than the configured smallest value, the emergency channel is enabled. The Service Controller cannot detect whether the third-party authentication server is active. If an exception occurs, user authentication cannot be done on the third-party authentication server. In this case, the FW acting as the SACG needs to check the health of the third-party authentication server. If the health status of the third-party authentication server is Down, the FW enables the emergency channel, ensuring service continuity. After the fault is rectified, the emergency channel is automatically disabled, and the original permission control for the user is restored.
It indicates the source IP address for initiating the interworking between the device and Agile Controller server. The Agile Controller server determines routes according to this IP address.
If the emergency channel is enabled, all permissions are available to users; otherwise, users have only original permissions.
If the result of either detection is abnormal, the emergency channel is enabled. The emergency channel is disabled only when the results of both detections are normal.
By configuring the Agile Controller server, you can add the Agile Controller server interworking with the device, and configure the port and pre-shared key for mutual communication between the device and the Agile Controller server.
Parameter |
Description |
|---|---|
Server IP |
Indicates the IP address of a Agile Controller server. |
Server Port |
Indicates the port used for the communication between the device and Agile Controller server, which must be consistent with the port of the Agile Controller server. |
Shared Key |
Indicates the shared key used for the communication between the device and Agile Controller server, which must be consistent with the shared key of the Agile Controller server. |
After you configure an authenticated URL, the system can use it to push web pages.
SACG statistics comprise the number of online users, online and offline information, COPS packet information, and error request count.