It has been two years since we released the last major versions of our products. In these two years, we were able to integrate a couple of great new features and a lot of smaller enhancements throughout all our products.
Let’s start with a feature which is probably most visible to the user: the User Interface. In Royal TS V5 (for Windows) we invested heavily in making the app even better in high DPI scenarios. All the icons are now based on SVG (vector based) images which allows us to render them with the highest quality based on the DPI setting of the system. In addition, we also introduced a couple of default color schemes (nowadays everyone seems to love dark themes). Users can also define and even share their own color schemes individually. Even the colors used in all the icons can be tweaked to ensure best readability and contrast. You can read more about the UI updates for Windows in this blog post.
On the Mac, we not only have macOS Mojave support, we also fully support Mojave’s dark mode. By default, Royal TSX will “follow” your preference from the OS but you can also switch to light or dark mode independently in the Preferences. In this Royal TSX (for macOS) release we also finally added support for splitting tabs and allow resizing the properties dialog.
We also know that our users love to configure their objects with custom icons. That’s why we included the open source VMware Clarity icon library in our custom icon picker.
One thing should be made clear: this is a game changer! Truly a first in the industry!
In a nutshell: you can write a script which populates a folder with connections, credentials, etc. dynamically based on your script output.
You may now ask: why do we (you) need this? Our main motivation came from a massive amount of feature requests about integrating with 3rd party systems like password vaults or PAM solutions or other data sources like Active Directory, AWS or Azure. It’s impossible for us to support and maintain each and every product out there. In addition, each user/company may use these products differently which makes it hard to support them in a way that all scenarios can be covered. But there’s one thing most of these products have in common: they have an API to access the data.
We already have a lot of sample scripts in our Github repository for various systems and we already have a growing community contributing to this repo. One of our users even posted a nice YouTube tutorial on how to make use of dynamic folders.
We support a variety of script interpreters on both platforms. All you need to do is, create a script which generates specific output (our well documented JSON format). With that, you can pull in data from everywhere you have script or API access to, and create your connections, credentials, tasks, subfolders, etc.
This has been on our todo list for quite a while. With the introduction of Royal Server and our deep Secure Gateway (automatic SSH tunneling) integration, we provided two object types called Royal Server and Secure Gateway. These object types helped you set up your connections and configure them to use the Royal Server or Secure Gateway to connect to.
We now have a similar concept for the Remote Desktop Gateway configuration. Instead of configuring the RD Gateway on each Remote Desktop connection, you can create a Remote Desktop Gateway object in your document and refer to the object from each connection (or even inherit it from its parent folder). This makes management and also credential assignment much easier. On top of that, you can also leverage the “Connect with Options” menu to either use a different Remote Desktop Gateway object or connect directly without the configured RD Gateway object.
Our newest releases of Royal TS and Royal TSX have much more to offer. To learn more about the new features in our apps and plugins, please check out the following pages:
In Royal Server V3 you can now configure which users/groups are allowed to use the document store component. Access rules, read/modify operations and grant/deny permissions for Windows users and groups are now supported.
You can enforce a second authentication (OTP) when a document is opened from a Royal Server. Our clients will prompt for the OTP (one time password) and only open the document when the code is valid.
One very popular feature of Royal Server is the Secure Gateway. It allows you to easily tunnel connections using SSH port forwarding through our server without the need of a 3rd party SSH server. So Royal Server is basically your SSH server and our newest release features a new core which is much more robust and secure. In addition, you now can control which encryption algorithms the client should use to tunnel your connections.
As mentioned above, this is one of the new key features of our new clients versions. Instead of executing the dynamic folder script locally on the machine where Royal TS/X runs, you can configure the dynamic folder to execute the script on the Royal Server.
A complete list of Royal Server improvements can be found here.
Our Chrome and Firefox extension also got a couple of noteworthy enhancements:
When you use the browser extension for the first time, Royal TS/X will now ask you if you want to allow access and trust the browser that is querying the data. By default, Royal TS/X will now also check if the browser process that is requesting the data, is actually Google Chrome or Firefox. In case you are using a different browser with the extension you may disable this check in the Preferences/Options under “Browser Extensions”.
In the past, our browser extensions only showed credential objects. With this release, we will now also offer web connections from your document(s).
If you assign a custom icon to your credential or web page connection, it will now also be shown in our browser extension.