Resolved issues for Standalone Sentry

Previous topic: Support and compatibility for Standalone Sentry Next topic: Known issues for Standalone Sentry

For resolved issues provided in previous releases, see MobileIron Sentry Product Documentation for that release.

The following issues are fixed in this release and are categorized into the following sections:

General resolved issues for Standalone Sentry 9.9.0

  • AL-14643: Previously, connections to share point server from Chrome browser on Windows using NTLM authentication failed. This issue is fixed.

  • AL-14709: Previously, when attachment control was enabled in Sentry and an email contained no MIME part boundaries, Sentry tried to encode the plain text mail content which caused distorted text when the mail content had umlaut characters. This issue is fixed.

  • AL-14720: Previously, special characters such as backspaces, quotation marks, and spaces were not allowed in the tenant password when registering MobileIron Sentry to Cloud or Access. This issue is fixed.

     

  • AL-14736: Previously, the tunneled proxy connect requests from a device to Sentry failed if the proxy listening port was 80. This issue is fixed.

  • AL-14842: Previously, requests sent from a device contained HTTP chunked data format. Sentry was unable to format the data correctly and send the data in multiple buffers to the associated proxy. This issue is fixed by handling the data in a single buffer.

  • AL-14864: Previously, the older versions of Sentry "Check Updates" displayed error "download failed" when no updates were available. This issue is fixed.

Standalone Sentry resolved issues for MobileIron Access

  • AL-14608: Previously, when Access was configured as a delegated IdP with Microsoft ADFS and DEL IDP with SAML assertion encryption disabled, users with accent characters (such as é, ô) in DistinguishedName or CanonicalName failed to log in to service providers applications. This issue is fixed.

Standalone Sentry resolved issues for MobileIron Core

  • AL-14584: Previously, when using a self-signed certificate for Sentry, clicking on Edit on Sentry settings in MobileIron Core and then saving without any changes, regenerated the self-signed certificate. This issue is fixed.

Standalone Sentry resolved issues for MobileIron Cloud

There are no new resolved issues that impact only MobileIron Cloud deployments.