Disabling CueWeb Authentication not working

[michimussato]

Describe the bug
I tried to follow @lithorus advice to bypass the cueweb authentication. I'm running a dockerized cueweb so I'm not able to comment out NEXT_PUBLIC_AUTH_PROVIDER but to set it to an empty string in the environment (as documented here). I would need confirmation that this has the same effect (or an alternate solution).

The full OpenCue setup is shown here:

As you can see, the opencue-cueweb environment looks as follows:

NEXT_JWT_SECRET=default-secret-key
NEXT_PUBLIC_AUTH_PROVIDER=
NEXT_PUBLIC_OPENCUE_ENDPOINT=http://opencue-rest-gateway.openstudiolandscapes.lan:8448
NEXT_PUBLIC_URL=http://opencue-cueweb.openstudiolandscapes.lan:3100
NEXT_TELEMETRY_DISABLED=1

Accessing the cueweb landing page, I'm still presented with the following authentication options:

The question is, is this expected? My intention is to bypass this step of authentication and delegate authentication to Pangolin.

@lithorus comment

It might be that the no authentication codepath is resticted to localhost only (development).

Cheers,
Michael

To Reproduce
As described.

Expected behavior
Bypass the cueweb authentication landing page on non-localhost setups.

Version Number
N/A