Releasing VQ Conference Manager 3.1

3.1 is available for download from; there’s a sense of relief here at VQ Towers that we finally delivered it. A huge amount of work went into 3.1 and it represents another big step forward. Some of the functionality might be described in small words (for example, Single Sign-on or “SSO”) but behind the scenes a lot of work went into getting the Open Id Connect (“OIDC”) Identity Server up and running; not only do we get SAML2 and Windows Authentication with it,  we can also now authenticate with services such as Google. It’s been quite an eye-opener to get exposed to state of the art authentication and the services provided by companies such as Okta (and their partners, JAMF and Yubico). From a technical perspective, I must admit I also found it remarkable how clean the mechanisms are and how, for example, access tokens are cryptographically signed and the consuming software can use the “time to live” value to know when the token expires. Very neat.

3.1 is an example of what is possible because of the architectural decisions we made for the 3.x platform; the OIDC certified Identity Server is hosted as a Container and is packaged as part of the VQCM 3.1 VM. Reactive Calls (aka Blast Dial) is another example of what’s now possible; it’s packaged as a small service that sits on the message bus and responds to events generated by the VQCM core.

Here’s a very high level overview of what’s in 3.1:

  • SAML 2 and Windows Authentication Single-Sign-On
  • Reactive-Call (aka Blast-Dial) functionality
  • Outlook plug-in
  • iOS App
  • Major update to Kibana dashboards and reporting
  • URI and Call Id generators allowing auto creation of URIs and Call Ids. Addition of a “Random” Generator
  • Support for Secondary Call Ids
  • Control Space creation, updates and deletes via the UX Profile
  • Disable the green + bar
  • Addition of a ‘now’ button to the schedule new meeting datetime picker
  • The VQCM user interface can be branded
  • Updates to the latest component versions (Centos, Kubernetes and Elasticsearch)
  • Space Template refinement to control participant level for join/leave tones

We hope you like it.