Programmatic login option for CONNECTION client or a web API for checking in/out licences

Having a programmatic way of logging into the CONNECTION Client is fast becoming a critical feature for our organisation as we start to implement automated cloud architectures which are dynamically creating virtual machines and need to be able to acquire licence seats dynamically. A programmatic login option would ensure a fresh login happens whenever a virtual machine is spawned rather than relying on a user to perform the login or relying on auto login working.

This programmatic login option could be either a command prompt / powershell interface that accepts username / password parameters to open the application and log in immediately. Alternatively, it could be a web API that removes the need for the CONNECTION client entirely, and instead allows for the programmatic checking in and out of licenses and issuing of tokens accordingly. The former seems easier to implement and would satisfy our immediate use cases.

I note that the auto-login process does not work consistently when spawning from machine images that were previously logged in even if the auto login token is periodically refreshed on the image. I also note that the offline licence feature is not viable here because instance names may change since the system creates them dynamically / on demand. Even if there was a way to guarantee the name persisted we would need to set aside a dedicated quantity of licences that would likely spend an undesirable portion of time sitting “checked out” for offline use but not actually in use.

Thanks for your consideration in adding this as a new feature!