Resolved Issues in the 6.11.10 Release
The following issues were fixed in the 6.11.10 release.
|
Bug ID |
Description |
|---|---|
|
CP‑50153 CP‑53874 |
Corrected an issue where, if the Guest module of a subscriber used the SessionAction API to send any request (including change of authorization (CoA) requests) to the publisher within the same zone, the request failed with a 404 error because the request path was not defined. |
|
CP‑52908 CP‑53479 |
Corrected an issue where an enforcement policy was incorrectly mapped if changes were made through a REST API call. |
|
CP‑53325 CP‑53881 |
Corrected an issue where trying to fetch the vendor name attribute for network devices failed through the REST API. The attribute is now included as part of the filtering criteria for the API. The value matching the can be found in the table. |
|
Bug ID |
Description |
|---|---|
|
CP‑53344 CP‑53814 |
Corrected an issue where ClearPass Device Insight profiling failed because Device Insight could not connect to ClearPass Policy Manager, and optikd (Device Insight) logs showed error messages with a 400 error code. This issue was caused by an expired certificate. With this fix, certificates are now automatically renewed and the event is logged. The Device Insight Integration certificate is valid for 360 days. At 180 days before it expires, a new certificate will be issued and ClearPass will use the new certificate. When automatic renewal is successful, the shows the message "Automatic certificate renewal for Optikd completed successfully." If the certificate renewal fails for any reason (for example, mismatched expiry dates), the shows the message "Automatic certificate renewal for Optikd failed," and the system continues to attempt the renewal. If the renewal continues to fail, please contact TAC for assistance. The old certificate still works until the end of the 180 days. |
|
Bug ID |
Description |
|---|---|
|
CP‑50698 CP‑53560 |
Corrected an issue where a bulk Import of endpoints or endpoint profiles did not trigger a Database Change Notification (DBCN) event, which caused the in-memory endpoints table to not be updated. Database updates for bulk imports of endpoints are now performed correctly. |
|
CP‑52056 CP‑53561 |
Corrected an issue where the wrong username was sent to the firewall for Session Logout events if the option was configured for the server at . |
|
CP‑52398 CP‑53594 |
Corrected an issue where Post Authentication tried to communicate with endpoint context servers using the HTTP Proxy even if the option was enabled at . |
|
CP‑52697 CP‑54174 |
Corrected an issue where, when trying to import an endpoints XML file, device profiling added invalid MAC addresses to the tipsdb.tips_endpoints table and the import failed. This issue was seen both with and without Device Insight integration. |
|
Bug ID |
Description |
||||||
|---|---|---|---|---|---|---|---|
|
CP‑50578 CP‑54171 |
Corrected an issue where, if an invalid phone number was entered in a guest registration form, the error message was shown but the form was allowed to be submitted and the account was created. The field is now correctly validated before the form can be submitted. |
||||||
|
CP-52261 CP-53876 |
If a login banner and forced user acknowledgment were configured in cluster-wide parameters for ClearPass Policy Manager user logins, they were also applied to ClearPass Guest operator logins and guest registration pages. This is still the default behavior; however, an option is now added in ClearPass Guest to override the Policy Manager setting. To disable or enable the Policy Manager banner and acknowledgment for Guest logins, go to .
|
||||||
|
CP-53143 CP-53567 |
Corrected an issue where the length of the randomly-generated MPSK password did not match the configured length. If a number larger than 16 was entered in the field at , ClearPass only generated a 16-character password. The MPSK password length is now increased to a maximum of 63 characters. |
||||||
|
CP‑53422 CP‑54116 |
Corrected an issue where the root partition (/) sometimes filled with too much data from the Guest application log and the showed the error message "System is runnning with low disk space. Aggressive cleanup for /$ will be initiated when the available disk space falls below 20%." Log rotation now limits the amount of data that is retained in the log file. |
||||||
|
CP-53788 CP-54179 |
Corrected an issue where a guest's email receipt was sent to them without a password if both the and options were configured under . |
|
Bug ID |
Description |
|---|---|
|
CP‑53327 CP‑54176 |
Corrected an issue where users with a custom operator profile that included full access to Insight could not fetch Insight alerts or reports through the REST API, and received a "403 Forbidden" error instead. Only users with the Super Administrator profile could use the API to fetch Insight alerts or reports. Now if a custom operator profile is created at and configured with (Read, Write, Delete) to API Services, plus at least minimum access (Read) to Insight in Policy Manager services, any operator with that profile can use the API to fetch Insight alerts and reports. |
|
CP‑53415 CP‑54006 |
Corrected an issue where, when Insight was configured to send email notifications for Insight alerts, the email showed the IP address instead of the qualified hostname of the server. |
|
CP‑53666 CP‑53797 |
Corrected an issue where Insight-enabled servers in a ClearPass cluster sometimes abruptly stopped working with alerts about the disk being full, and multiple error log files were generated for the /var partition. For customers who have implemented the workaround cron cleanup script with TAC's assistance, th e 6.11.10 cumulative patch will automatically remove that process. Customers who have not implemented the workaround are not negatively impacted. |
|
Bug ID |
Description |
|---|---|
|
CP‑48227 CP-45201 CP-54170 |
Corrected an issue where, although license computation should only run on the publisher, license computation was running on an Insight-enabled subscriber in a cluster. The license computation is now correctly run on only the publisher and not run on any subscribers (Insight-enabled or not). |
|
CP‑53990 CP‑54167 |
Corrected an issue where, if there were one or more expired licenses for the cluster, then after the daily cron job was run for license entitlement or license add/update events a very large number of license entitlement processes caused high CPU-usage and load-average issues. |
|
Bug ID |
Description |
|||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
CP‑52402 CP‑53563 |
Corrected an issue on Ubuntu clients where the ClearPass OnGuard Agent sometimes failed to connect to the ClearPass Agent Controller service after the interface was bounced. |
|||||||||
|
CP‑52857 CP‑53565 |
Corrected an issue on Ubuntu clients where RADIUS authentication did not happen after the OnGuard Agent bounced the wireless interface. |
|||||||||
|
CP‑52873 CP‑53768 |
Corrected an issue where the ClearPass OnGuard Agent caused the Ivanti application (ST.EngineHost.exe) to stop abruptly. |
|||||||||
|
CP‑52889 CP‑53769 |
Corrected an issue where a Windows client was marked as unhealthy when all of the following conditions were true:
|
|||||||||
|
CP‑52948 CP‑53770 |
Corrected an issue on macOS clients where the ClearPass OnGuard Agent displayed messages that requested access to some privacy settings. |
|||||||||
|
CP‑53400 CP‑53771 |
Corrected an issue on macOS clients where the ClearPass OnGuard Agent bounced the interface after waking from sleep even when the file was present. |
|||||||||
|
CP‑53410 CP‑53882 |
Corrected an issue on Windows clients where the ClearPass OnGuard Agent sent an empty list instead of the missing patches for a Patch Agent application if a previous attempt to read the missing patches had failed. |
|||||||||
|
CP‑53688 CP‑53740 |
Corrected an issue on Windows clients where the ClearPass OnGuard Agent did not detect the Check Point Endpoint Security 88.x application. Support is now added for Check Point Endpoint Security 88.x. |
|||||||||
|
CP‑53823 CP‑54024 |
Corrected an issue on macOS clients with an M1 chip where the ClearPass OnGuard Agent installer showed a message saying the Rosetta emulator had be installed. |
|||||||||
|
CP‑53984 CP‑53997 CP‑53998 CP‑54025 |
Corrected an issue on macOS 15 (Sequoia) clients where OnGuard displayed the error message "Failed to connect to ClearPass Agent Controller Service." The ClearPass OnGuard Agent for macOS is now supported on macOS 15. |
|||||||||
|
CP‑54016 CP‑54223 |
Corrected an issue on Linux clients where the VIA component of the ClearPass OnGuard Agent did not send the value of the field from the selected certificate as the username in the WebAuth request. Instead, the OnGuard Agent sent the value of the field as the username, which caused authentication failures. This issue was only seen when certificate-based authentication was enabled. The VIA component now correctly uses the UserPrincipalName (UPN) from the SubjectAltname attribute. If the UPN is not available, the application falls back to using the CN value of the certificate. |
|||||||||
|
CP‑54106 CP‑54107 |
Corrected an issue on macOS clients where the ClearPass OnGuard Agent did not report the correct status for "Mac OS X Builtin Firewall 15.x" on macOS 15. The ClearPass OnGuard Agent for macOS is now supported on macOS 15 and correctly reports status for "Mac OS X Builtin Firewall 15.x". |
|||||||||
|
CP‑54241 CP‑54273 |
Corrected an issue on Windows clients where the OnGuard Agent displayed certain characters incorrectly for the Spanish language. |
|
Bug ID |
Description |
|||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
CP‑51534 CP‑54172 |
Corrected an issue where the page of the publisher became uresponsive if one of the subscribers was unavailable. |
|||||||||
|
CP‑52203 CP‑53562 |
Corrected an issue where, at , rows for requests in TIMEOUT status were displayed in yellow font. The font color reverted to black if the user clicked the row, but sometimes turned yellow again if the page was reloaded. This was a cosmetic issue and could be ignored. |
|||||||||
|
CP‑52645 CP‑53564 |
Corrected an issue where, when an enforcement profile that had the option configured on the tab was exported and then imported in again, the VLAN names were treated as a single entry all on one line. Now when the enforcement profile is imported the names are properly treated as different entries on separate lines. |
|||||||||
|
CP‑52690 CP‑54253 |
Corrected an issue where, after ClearPass was updated, the server's number in the "Last successful login" banner and the URL was displayed as an encrypted IPv6 address. |
|||||||||
|
CP‑52772 CP‑53877 |
Corrected an issue where the default route was sometimes lost during a change to the maximum transmission unit (MTU) and an incomplete restart of the NetworkManager service. |
|||||||||
|
CP‑52924 CP‑53879 |
Corrected an issue where ClearPass could not retrieve data properly from MSSQL server 2016 or 2017 as part of authentication or authorization sources. |
|||||||||
|
CP‑53106 CP‑54113 |
Corrected an issue where frequent restart of some important services in the system (ClearPass system-auxiliary-service, RADIUS service, etc.) were seen if the syslog server was configured as the Fully Qualified Domain Name (FQDN). |
|||||||||
|
CP‑53416 CP‑47008 |
Corrected an issue where, at , the graph displayed the available space for only the partition (the root) instead of the total available space for the partition. Now for the selected server, in addition to showing the graph for the root partition the page also includes graphs for the and partitions. The three graphs are interpreted as follows:
|
|||||||||
|
CP‑53519 CP‑53942 |
Corrected an issue where, an action was selected in the user interface that opened a pop-up window (for example, an add, import, or show-details action), sometimes the pop-up window displayed the error message “Sorry, an error occurred” instead of the expected content and the action could not be completed. |
|||||||||
|
CP‑53584 CP‑54187 |
Corrected an issue where Database Change Notification (DBCN) processing sometimes failed with the error message "[Errno 24] Too many open files," and as a result ClearPass did not apply the changes in OnGuard Application Access Control. This issue was seen when the number of file descriptors opened by the cpass-dbcn-daemon service was more than 1024. |
|||||||||
|
CP‑53782 CP‑54073 |
Corrected an issue where service categorization failed for a device group if the group included both a NAD subnet and an IP address range. |
|||||||||
|
CP‑53993 CP‑53995 |
Corrected an issue where the HPE Aruba Networking 5420 switch was not able to communicate with ClearPass using its Trusted Platform Module (TPM). The root certificate authority (CA) is now added to the ClearPass Trust List. |
|||||||||
|
CP‑54019 CP‑54441 |
Corrected an issue where, if a chain of elliptical curve (EC) certificates included an intermediate CA with explicitly-defined curve parameters, ClearPass accepted the certificate for IPsec connections. ClearPass now rejects an EC certificate chain if it contains an intermediate CA with explicitly-defined curve parameters instead of named curve parameters (for example, secp256r1) |