Noteworthy Information
3 min
- Outbound HTTP/HTTPS proxy connections are restricted to a defined allow list of well-known proxy ports to align with Secure by Default. Allowed ports: 8080, 8118, 8123, 10001–10010, 10080, 3130, 3445, 8008, 8010, 3128.
- Feature parity with IPS release 22.7.R1.14.
- Starting with IPS version 25.1.x.x the default global (System > Configuration > Client configuration) and Role level (User > User Roles > <name> > Ivanti Secure Access Client Settings) options for the ISAC Desktop user experience (UX) is set to NewUX for fresh installations of IPS.
- Ensure your environment allows installation and execution of the React Native AppX bundle used by NewUX.
- Follow the guidance in the forum article to enable the AppX bundle.
- Applies to: New installations to IPS 25.1.1.2 and later.
- Cluster upgrade is not supported from 22.8.R2.4 (1867.1). To upgrade, break the cluster, upgrade and then create the cluster again. For more information, see Cluster Migration from 22.8Rx to 25.x. For more information, see Cluster Migration from 22.8Rx to 25.x
- SAML Authentication Server configuration using the SAML 1.1 Protocol is deprecated in IPS 25.x versions. From 25.1.1.2 onwards, the system will not allow new SAML 1.1 server configuration and will not allow to import any existing configurations. SAML 2.0 is the option supported. This deprecation was initially notified as part of this KB.
- Before performing a push Config operation from an older release to version 25.1.1.0, you must disable the HTTP Only Device Cookie on the target device.
- For Admin Roles: Navigate to Administrators > Admin Roles > Delegated Admin Roles > Administrators > Session Options.
- For User Roles: Navigate to Users > User Roles > [Role Name] > Session Options.
- Referrer header validation is enabled by default to block CSRF attacks, providing an additional layer of security.
- All cookies will be deleted upon session terminated by default, enhancing security and privacy.
- The Next Generation Web Server (Nginx) will restart when performing any of the following certificate-related operations. User connections may drop during this period.
- Mapping a device certificate to a port.
- Importing or deleting a trusted client CA.
- Making changes to inbound TLS versions and cipher suites.
- IPS License Server cannot lease licenses to License Clients running versions 22.7Rx, 22.8Rx, or 25.1.x.x. For more information, see forum link. The information in this article is applicable for IPS as well.
- Certificate based authentication will not work after upgrading to 25.1.x.x, if client uses SHA-1 based certificates.
- SSLv3, TLS1.0 and TLS1.1 versions are removed and there are additional cipher changes implemented as part of this release. For more information, see Configuring SSL Options.
- Use of SHA1 for digital signature is not supported, use SHA2 and above:
- SHA2 is the minimum required version in digital signatures. IPS will no longer connect or validate with SHA1 in digital signatures.
- Enable SHA2 as response signature algorithm in OCSP response on OCSP responder.
- If the IPS only contains SHA1 device signed certificates, the user interface fails to launch. At least one SHA2 signed certificate or any newer version after SHA1 is mandatory.
- Certificate Validation: HTTP/1.1 Enforcement for OCSP Requests Starting with version 25.1.x.x, certificate validation process now explicitly enforces the use of HTTP/1.1 for Online Certificate Status Protocol (OCSP) requests. This ensures consistent and reliable communication during certificate status checks. For more info refer KB.
- In this release, the /api/v1/healthcheck REST API response has been updated to return content as bytes, which aligns with the default behavior of many web frameworks and libraries when handling API responses. Previously, the response was returned as a string. This change could impact systems or integrations assuming the response would always be a string.
- Upgrade or Binary Import is not supported if SHA-1 certificates are configured on any IPS ports.
- Configs with deprecated features will be upgraded or imported to 25.x but will not be qualified. Refer the KB for more details
- arping command no longer resolves hostnames. The command now requires a direct IP address as input. Attempts to use hostnames will result in an error. Example error: Bad Value for ai_flags. Don’t use a hostname with arping.
- The ARP Maintenance >Troubleshooting >Tools >Commands>ARP option no longer supports hostnames as input. You must now specify a direct IP address when using this command. Attempts to use hostnames will result in following error. Example error: Bad Value for ai_flags. Don’t use a hostname with arping.
RSA Authentication
- For RSA Authentication to work, Add the agent's host name in RSA Auth Manager and configure it in IPS. Ensure the RSA/ACE server has a host entry in IPS.
- TCP is now enforced as the only supported communication protocol for the RSA SecurID integration. Legacy UDP-based communication is no longer supported.
- Update firewall rules to allow outbound TCP from IPS to the RSA Authentication Manager on the configured SecurID agent port(s) used in your environment, see KB for more details. The information in this article is applicable for IPS as well.
- As TCP is used, hostname-based validation is mandatory. As a result, the Hostname configured in IPS (Network → Overview) must match the Agent Hostname defined in the RSA Authentication Manager.
- This replaces the earlier flexibility of using internal IP addresses, which was possible with the legacy UDP-based integration.
- The above scenarios apply to RSA Authentication Manager 8.7 and below.