I’ve been running Open OnDemand with the Open XDMoD integration. It works fine in Firefox, but has issues in Chrome/Edge. It worked up until recently, I get the same timeout messages shown in Did anyone have a success integrating XdMod and OnDemand? . This happened when we first set it up and we were able to get by it by setting this in /etc/httpd/conf.d/xdmod.conf on our XDMoD server:
That directive is still there but we’re back to getting the timeout messages. It would seem this is a result of some security setting that is present in Chrome/Edge but not Firefox.
I did discover that if I go to edge://flags/#local-network-access-check and set Local Network Access Checks to Disabled then it works fine again. Not sure that’s a scalable answer, but at the very least going to note it for anyone who runs into the same issue and finds this thread.
Thanks for looking. I’m not great with browser debugging, the best thing I can find in the network tab is probably “An error was encountered while attempting to process the requested authorization procedure.” Microsoft Entra ID is what we’re using for our IDP. Perhaps the real issue is on that side and not the Open OnDemand side? I ran through some of this through Claude because that’s what people do these days. It thought it might make sense to add a targetAddressSpace: ‘private’ to fetch calls in xdmod.js. Not sure if that suggestion is valuable or a hallucination.