Distributed Config and Render Farm Setup

[philip.scadding]

@matt_ce

I’m not sure if this has unexpected negative consequences, but it’s been working fine for us so far.

I’m not a 100% certain, but I imagine that it would fail if the job was left in the queue for too long as the session token would expire and it wouldn’t be able to authenticate without the user re-entering their user name and password.
Another approach you could take would be to use script authentication and then do something similar to what’s covered here:

Creating user sandbox folders without needing the user to work on the task

If you have set up user sandboxes in your config’s schema, by default they only get created when a user goes and saves a scene in that context. However, there can be times where you want to create them manually in a one-off step. For example If you would like to create them up front without the user needing to create a new scene file in workfiles on the task. You had to unregister existing user folders and now you want to re-register them, you will need to use a script to do this. Here is an …

Essentially the get_current_login.py hook could return back the SG user name that you could provide in an env var.