By Oana Bota
The recent release of Netop Remote Control version 12.60 includes new features like support for Windows Server 2016 and an email based multi-factor authentication option. You can learn all about the new release here , but if you ask me, the real excitement won’t be found in the release notes or be seen on the promotional pages of the website.
Don’t get me wrong, the new multi-factor authentication service provided at no additional cost to customers is great. That one feature provides a ton of value, but take a look under-the-hood of this release and you’ll see a whole new world of possibilities opening up.
First, we updated the architecture of the Netop Portal. We have decoupled the authentication process from the other services the Netop Portal provides (e.g., authorization and connectivity). This continues the broader architectural change we began last year, moving away from the traditional monolithic service-oriented architecture to a modern, cloud enabled microservices architecture.
The shift to microservices not only provides huge improvements in scalability, but also holds the promise of greater flexibility. What does the future hold for authentication options from the Netop Portal – ADFS, LDAP, RADIUS, oAuth2? All these options are being reviewed and prioritized for a possible future release.
Second, we made important changes to our Guest module. Version 12.60 has expanded authentication options in the Guest to take advantage of the capabilities now available in the Portal: the Netop Remote Control Guest & Host connections now have an email based multi-factor authentication option provided by the Netop Portal. As new capabilities are added to the Netop Portal (again, think ADFS, RADIUS, RSA SecureID, etc.) they will become immediately available to the Guest & Host – without reinstallation, update, or changes to the Guest & Host configuration.
Consider for a moment all the authentication options now available in Netop Remote Control. You can use proprietary Netop authentication, rely on Active Directory or LDAP, and integrate with a RADIUS, Windows Azure or RSA SecureID server. Authentication can be managed locally, through an on-premise server, or through our hosted, cloud-based portal.
Whatever your authentication needs – with Netop Remote Control version 12.60, it’s almost certain we can meet them. These improvements in version 12.60 are aligned with our mission to develop Netop Remote Control in ways that benefit our customers most, and there is plenty more of that to come.
Source:: netop blog