|Date||Description||Found in Release||Fixed in Release|
|June 28||You can now access the private applications over RDP and SSH when their IP address is configured. (Windows)||6.1.0||6.1.2|
|Aug 10||The latest SAML Authentication policy configured under Web Policy is skipped for Private Applications.||6.1.0||6.1.2|
|Date||Description and Workaround (if any)||Found in Release||Fixed in Release|
|Jun 27||Failed to publish updates due to a hostname conflict when the Clientless Access option is enabled along with displaying an incorrect error message.||6.1.0||-|
|July||Clientless Access does not support Remote Browser Isolation policy.||6.1.0||-|
Fail to access the private applications over RDP and SSH when the IP address of these applications are configured. However, the HTTP/HTTPS protocol works for such configurations. (macOS)
Workaround: Configure the host name of the private applications for the RDP and SSH protocols.
The username used for SAML IDP authentication becomes case-sensitive when you enable the Clientless Access option.
Workaround: Enter the username in the same case as it was created.