Skip to main content
Skip table of contents

Blue Cedar Platform Release Notes - October 13, 2021

Blue Cedar Platform 5.3.0

Blue Cedar Enforce No-code Integration - Blue Cedar Enforce Branding

Added support for Blue Cedar's No-Code Integration Service for Enforce which embeds Blue Cedar Enforce app security into mobile apps without writing code. Blue Cedar Enforce is not dependent on any unified endpoint management (UEM) solution and provides protection for data in mobile apps on managed and unmanaged devices.  App security controls that are enabled by this no-code integration include: 

  • Data Encryption which uses device-independent encryption to protect data-at-rest.

  • Device Posture which requires various attributes (e.g., minimum OS version, jailbreak/root detection, device screen lock) be met prior to allowing the app to execute.

  • Data Loss Prevention (DLP) which prevents copy/paste between protected and unprotected apps

  • Authentication (e.g., fingerprint, require PIN/passphrase, etc.)
 for device screen lock

See the referenced online documentation pages for more information, or click Help when you’re logged into the Blue Cedar platform.

Blue Cedar Connect  

Blue Cedar Connect enables secure access to corporate data with an in-app VPN that is optimized for mobile environments.  When the Blue Cedar Enforce extension is enabled, it provides the option to embed the Blue Cedar Connect in-app VPN client.  The in-app VPN client works with Blue Cedar Enforce and makes it easy for a mobile app to connect to resources behind the firewall, even if the app is running on an unmanaged device. 

  • Blue Cedar Connect for securing access to corporate data with an in-app VPN client. 

What do I need to do?

To use the Blue Cedar Enforce no-code integration, first enable the corresponding extensions and then add the steps to your workflows.

To add Enforce to a mobile app:

Microsoft Intune no-code integration - multi-tenant apps 

Blue Cedar's No-Code Integration Service for Microsoft Intune now supports configuration of the app to accept the multi-tenant sign-in for providing apps to many organizations using different Azure AD tenants.

What do I need to do?

To use the Microsoft no-code integration, first enable the corresponding extensions and then add the steps to your workflows.

To add Intune to a mobile app:

  • Enable the Intune extension listed under No-Code integration, as described in Extension - Microsoft Intune. You don't need to add any extension configurations for Intune.

  • Add the Intune workflow step to an App container under the App Enhancement stage in the Workflow Builder. Configure the step as described in No-Code Integration - Microsoft Intune.

  • For mulit-tenant, select that option in the Microsoft Intune configuration Step.

Additional notes on the Microsoft integrations:

  • While you can add Intune without having to include the Endpoint Manager in your Blue Cedar integration, you cannot add the Endpoint Manager step unless you've first added the Intune step.

  • The Microsoft and BlackBerry no-code integrations are mutually exclusive. Adding either of these steps to a workflow disables the other options. You can see options in new workflows for any extensions that have been enabled.

Enhance Service

Updated the Blue Cedar Mobile Client version 4.11.0 to include Apple iOS 15 support.

Mobile Client 4.11.0 Update

Apple iOS 15 support. Apps that were previously integrated with Blue Cedar and that worked on iOS 14 are expected to work without issues when reintegrated with Blue Cedar. Apps that target new APIs and features for iOS 15 may have issues.  This release supports the BlackBerry version 9.1 SDK.

iOS limitations

Limitations with this Blue Cedar release for iOS 15 apps include: 

  • Focus and system filter notifications and apps based on your activity

  • HLS HTTP Live Streaming adaptive bitrate communications protocol for HTTP live streaming

  • Photos picker: a way to access pictures from the Photo app without requesting direct library access

  • App Clips: small parts of an app designed for quick task completion

  • Widgets: small app instance that's updated in the background and refreshes information on your home screen

  • WKWebView for data persistence handling, such as HTML5, Web SQL

  • UIScene support for multiple app windows

Resolved in Mobile Client 4.11.0


Mobile OS






Fixed an issue with interactive MSAL authentication for tunnel re-connect, which can be required for Conditional Access policies like Multi-Factor Authentication.




Fixed an issue for opening files using a temp directory.

Resolved Platform Issues

Apps and workflows




Fixed a bug to support long app names.


Fixed a bug for loading the apps list with window resizing.

BlackBerry Service




Added validation for the GDApplicationID across workflow steps to support the BlackBerry UEM requirements.


Added a validation for the BlackBerry UEM extension configurations during create and update.

Microsoft Service




Added  checks in the Blue Cedar Connect sub-step to validate the certificate expiry date.





Fixed an issue to allow column sorting on the Artifacts page.


Fixed a bug to support long app names.  


Added the name of the app deleted in the notification message.


Fixed an issue to handle displays when loading workflow information on the Artifacts page.


Fixed a bug that prevented the warning icons next to a field on app binary details page from displaying tooltip details.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.