The POST method performs a disconnect on active sessions with a synchronous or asynchronous action. This API is available at Guest > Administration > API Explorer > DynamicAuthorization > SessionAction.
#LANSWEEPER API MAC#
The SessionAction API directly handles both disconnect and change of authorization (CoA) actions for endpoints by either MAC address, username, or Framed-IP-Address. It includes synchronous or asynchronous action, and enhanced filters for flexibility and improved user experience.
GlobalServerConfiguration > AdminUserPasswordPolicyĪ new SessionAction API adds support for performing disconnect or reauthorize actions on active sessions. UsersAndPrivileges > AdminUserPasswordPolicy GlobalServerConfiguration > AdminPrivilege LocalServerConfiguration > ServerConfiguration
GlobalServerConfiguration > PolicyManagerZone GuestCojnfiguration > GuestAuthenticationConfiguration Platform > GuestAuthenticationConfiguration GlobalServerConfiguration > ClusterWideParameter GlobalServerConfiguration > ClusterDbSync GlobalServerConfiguration > OperatorProfile GlobalServerConfiguration > ListAllPrivileges GlobalServerConfiguration > MessagingSetupĬertificateAuthority > CertificateRequestĮndpointVisibility > OnGuardGlobalSettings GlobalServerConfiguration > ApplicationLicense
GlobalServerConfiguration > LocalUserPasswordPolicy ToolsAndUtilities > RandomPasswordGenerator GuestActions > GenerateActiveSessionReauthorize GlobalServerConfiguration > SnmpTrapReceiver GlobalServerConfiguration > FileBackupServer Integrations > ExtensionInstanceReinstallĮndpointVisibility > ProfilerSubnetMapping GlobalServerConfiguration > ClearPassPortalĮndpointVisiblity > FingerprintDictionary PlatformCertificates > CertTrustListDetails New API Explorer Structure and Names Starting in 6.9.3ĮndpointVisibility > AgentlessOnGuardSettingsĮndpointVisibility > AgentlessOnGuardSubnetMapping Table 1: Comparison of API Structure and Services Name Changes in Previous Releases and the 6.9.3 Release For more information about each API, go to Guest > Administration > API Services > API Explorer. The modified service names are highlighted in bold font. All API names are changed, some service names are changed, and services are rearranged into different categories. The following table maps the REST API's previous structure and service names to the new structure and service names. In addition to these usability features, these enhancements also make the ClearPass REST API compliant with the Aruba Developer Hub, providing readiness for any future API portal changes and growth. These changes do not impact the API functionality at all, and will have no effect on current customer deployments only the names and display hierarchy are different. (CP‑40005, CP‑40527) Features Added in 6.9.3Įxtensive changes in the ClearPass REST API display structure provide more logical categories, names that make each API's function easier to identify, and improved metadata text for some API services. Allowing unencrypted TACACS+ authentication requests to be processed is not recommended for production environments. To continue the default behavior of dropping unencrypted TACACS+ authentication requests, leave the value of the TacacsAllowUnencryptedCommunication parameter set to Disable. The default value for this parameter is false ( Disable). When this parameter is set to false, the TACACS+ module will drop TACACS+ requests from network access devices (NADs) that do not have a shared secret or do not have an unencrypted flag set in the TACACS+ header. A new REST API parameter, TacacsAllowUnencryptedCommunication, is added for TACACS+ authentications at Guest > Administration > API Services > API Explorer > GlobalServerConfiguration > ClusterWideParameter.
0 kommentar(er)
