Corel (now Alludo) Acquires Awingu to Accelerate Its Secure Remote Workspace Offering. Read more

Awingu introduces version 4.3

Thursday December 5th, 2019, Ghent (Belgium), New York (United States) – Today Awingu launches its new product release with Awingu version 4.3. This version will add new functionality in 3 main categories: Single Sign-On (SSO), User Experience enhancements and Admin improvements.

The following gives a short overview of the individual topics. In this blog post, we will deep dive into a subset. More information will be available in this webcast.

  • Use an external IdP together with Awingu (SAML & OpenID Connect)
  • Multi-monitor
  • 3 finger panning on tablet
  • Optional polygon
  • Context menu in sidebar
  • Simplified Application management


1. Single sign-on

Already in previous versions of Awingu, Single sign-on (SSO) was supported. In Awingu 4.3 we’ve added the possibility to fully leverage an external Identity provider such as Okta, Microsoft Azure AD, ADFS or Google Identity. 

To put some structure into Awingu and SSO, we should first identify 2 levels at which SSO occurs. (A) between the user and the Awingu workspace and (B) between the Awingu workspace and the applications/desktops/files running in the back-end. The below pictures shows this.

2 levels where authentication takes place

In (A), Awingu was typically used in conjunction with a classic Active Directory and Windows credentials. Users typically needed to authenticate when surfing to their login URL in the browser. Most Awingu customers have an additional MFA login on top.
Now, in Awingu 4.3, users can authenticate with an external IdP (e.g. Microsoft ADFS, Microsoft Azure AD, Google, Okta) and automatically be authenticated into Awingu also: i.e. users don’t need to add any credentials anymore. Furthermore, all security services (such as MFA, geofencing, …) offered by the IdP can also be used for Awingu. Awingu can connect with IdP’s that support “SAML” & “OpenID Connect” standards.

In (B), Awingu already offered SSO with RDP based apps & desktops, with intranets and internal web applications, with a set of SaaS services*, and with file servers. This will keep being the case when using an external IdP (exception of the reverse proxy and WebDAV).

The below pictures illustrates the overview of scenarios. Contact the Awingu team when you require more information on the technical setup & the different scenario’s.

Different SSO scenario’s with Awingu 4.3

Having full SSO available enables some other interesting scenarios, such as running Awingu in a fully Google operated environment or adding legacy apps streamed with Awingu in the Office 365 interface.


2. UX Enhancements

Multi-monitor working

Awingu 4.3 adds full multi-monitor support while running inside a browser-only session (no local agents/plug-ins/… are required). Up to 16 physical monitors can be used (RDP limitation). Session recording – can be activated for compliance reasons for example – across all screens is supported.

Activating multi-monitor usage is easy via the Awingu ‘polygon’ inside an application session, or via the context menu. The context menu can be activated through a right mouse click on the application icon in the Awingu navigation bar (see below). Note: on touchscreen devices (excl. iOS), ‘long tap’ can be used to pull up the context menu.

Working multi-monitor with Awingu 4.3; example with 2 external monitors connected to a laptop, 3 monitors in total

Noting that Awingu already supported – and keeps supporting:

  • Browser screen stretching (e.g. for large .xls documents)
  • ‘open in new tab’ for streamed applications (e.g. published version of the Outlook app on screen 1 and published version of Excel app on screen 2)
Hide the Awingu Polygon

The Awingu ‘polygon’ was introduced in Awingu 3.0 (some users call it the Awingu ‘button’) and allows users to pull-up application session-specific features such as working multi-monitor (Display Manager), Copy/Paste (on touch devices), ‘open in new tab’ or share session.

As of Awingu 4.3, the Polygon can be removed via the user actions (click the user icon at the bottom left). This needs to be done by the user, for each of the browsers and can not be pushed by the admin for all sessions/users.

The session-specific functions will become available in the form of a ‘context menu’ in the Awingu navigation bar (left of the screen). The context menu can be requested with a mouse right-click, or, with ‘long tap’ on a touch device.

The state is remembered per browser. It can be changed at any time via the user actions menu (bottom left). Note: The Polygon can not be removed when using an iOS device (as iOS devices don’t allow ‘long tap’ to pull-up the context menu).

How to hide the Awingu ‘Polygon’ and use the context menu

Awingu 4.3 feature overview video

Watch our Awinguru’s explain the details of this release with a live demo via the video below!

Find out more about Awingu!

About the author
arnaud square
Arnaud Marliere

Chief Sales & Marketing Officer

Table of contents
Want to learn more about Awingu?
This website uses cookies. Read our transparent cookie policy!