Hi: This is something I wish the docs would actually have expanded a lot more on since a lot of my fumbling around the past few months was specifically trying to decide the best way to do this. Initially I had it the same way you're intending, with each ftrack application reading from a specific auth file that sets the environment variables and then launches the application in a subprocess (Connect/3ds max). Right now though I'm abandoning that approach since it's becoming a hassle to manage, and just have a new standalone application for entering credentials. That writes to a global QSettings file instead that is now read and sets the environment variables directly. This way multiple users can still login on the same machine and avoid having to manually set environment variables all the time.
Hi: This is something I wish the docs would actually have expanded a lot more on since a lot of my fumbling around the past few months was specifically trying to decide the best way to do this. Initially I had it the same way you're intending, with each ftrack application reading from a specific auth file that sets the environment variables and then launches the application in a subprocess (Connect/3ds max). Right now though I'm abandoning that approach since it's becoming a hassle to manage, and just have a new standalone application for entering credentials. That writes to a global QSettings file instead that is now read and sets the environment variables directly. This way multiple users can still login on the same machine and avoid having to manually set environment variables all the time.