On Mon, Jun 6, 2022 at 6:33 PM Vieri <[email protected]> wrote:
> On Sunday, June 5, 2022, 03:02:35 PM GMT+2, Nick Couchman < > [email protected]> wrote: > > > > > Yeah, I think the issue, here, is that Windows does not "know" the > difference between URLs within the browser - it just knows that either > Firefox is running, or it is not. I'm not sure > > that Remote App can actually solve your issues, here. > > RemoteApps and Firefox in kiosk mode were mentioned several times on this > list for this purpose. > > Yes, I'm likely the one who has mentioned it, in response to queries about Guacamole supporting HTTP(S) as a protocol. There are probably situations and configurations that could work out, but there are certainly challenges to work through and maybe even things that won't work. My mentions of it have been, to my recollection, generic and theoretical, and certainly in need of proving in the real world :-). I'll try to get some time to play around with a more real-world configuration and see if I can get something to work. > Since kiosk mode does not work for me I tried using userchrome.css to > disable most GUI components and launch Firefox as a private window. The > user cannot do anything useful except close the browser by clicking on the > window X button. It works a lot better than in kiosk mode. However, I'm > using a common "profile dir" for all RemoteApp instances (multiple users). > Despite launching in "private window" I0m still unsure this is "safe" to be > used in a multi-user environment. > > Cool, this sounds like a workable solution. As far as the shared profile directory, if it were me, I would certainly launch each individual user with a different/separate profile, but you can find a configuration that works for you. -NIck
