Using OIDC/Okta authentication on the Horde Server seems to not work well with Horde Agents and UBA - does anyone have a working setup and know how to configure this?
I am setting up Horde for Remote Compilation - specifically with the goal of running agents on our developer machines and utilize them when idle.
I have managed to configure the server to use Okta OIDC for authentication and I can access the web UI and log in via Okta.
However, when I try to connect my local Horde Agent, managed with the Unreal Toolbox, or start a build with Unreal Build Accelerator through Unreal Game Sync, in both cases they connect to my Horde Server, go through authentication in a browser with a success result, but then give the following error:
Unreal Toolbox:
Connection failed: Value cannot be null. (Parameter 's')
UGS:
Unable to create Horde session: Value cannot be null. (Parameter 's')
I have configured ACL for my user in the globals.json file, both in the top level ACL section and in the plugins.compute.clusters, as described in the documentation.
I have tried disabling authentication and then I have no issues connecting an agent (using an agent registration token) or connecting from UGS/UBA.
There seems to be no good documentation on how the Agent or UBA/UGS is supposed to work with authentication, but there’s almost nothing to configure on the client side, so I’m guessing I’m missing something on the server.
Anyone had similar issues or been able to get things working with Okta/OIDC auth?