Insights dont show on public - E401

marhul · March 24, 2025, 12:28pm

I’m a newbie. First of all, thank you for OR being here.

I want to make “Insights” visible without logging in.

I’m running the latest version of OR on a VPS with Ubuntu 20.

I have a single asset that measures temperature and humidity. The asset has the “Public read” option enabled, and both the humidity and temperature attributes are also set to public.

I created an “Insight” with two widgets (temperature + humidity). In the insight settings, I selected Permissions > View > Public.

When I’m logged in, the Insights link works as expected:
https://iot.xoxofoto.cz/insights/?realm=master#/view/[ID of insights]/true

However, when I open the link in an incognito window, I see an E401 error in the console, and the screen is completely blank.

The console shows the following error request:

GET request to https://iot.xoxofoto.cz/auth/realms/master/account  
Response: {"error": "HTTP 401 Unauthorized"}

What I doing wrong?

martin.peeters · March 24, 2025, 1:40pm

Hi!

I think this is a bug that is accidentally introduced, being unaware of ‘public’ apps like Insights.
As I can reproduce it on our demo (OpenRemote Insights), I’ll raise a GitHub issue on this.
Thanks for reporting!

martin.peeters · March 24, 2025, 1:47pm

github.com/openremote/openremote

Unauthorized access to Insights app is not allowed

opened 01:45PM - 24 Mar 25 UTC

MartinaeyNL

Bug

### Describe the bug A user on the forum reported the following issue; https://f…orum.openremote.io/t/insights-dont-show-on-public-e401/3750 You're not able to visit the `/insights` standalone app to view dashboards. It's not required to be authenticated to access this web page. There is no auto-redirect to a login page if you're unauthenticated. However previously, the web app is shown like normal, now a blank screen is presented. ### To Reproduce Steps to reproduce the behavior: 1. Go to https://demo.openremote.app/insights/?realm=smartcity in an incognito (or new) window. 2. The screen stays blank (because you're unauthenticated), and an error appears in the network logs. ### Expected behavior The `/insights` web app should be publicly accessible, and should not require authentication.

abra · April 28, 2025, 7:41am

I seem to be having the same issue.

Has this been resolved? Does anyone know of a workaround?

martin.peeters · April 28, 2025, 8:24am

Hi, welcome to the forum!

The GitHub issue I’ve created (linked above) hasn’t been picked up nor resolved yet.
I’ll try to pick it up when I find the time, although I’m quite busy at the moment

Unfortunately I’m not aware of a simple workaround, other than making users login.

This bug got introduced due to a change on November 15th, 2024.
Only manually building the Docker images will allow you to deploy OpenRemote without this bug.

abra · April 30, 2025, 6:25am

Unfortunately I am not familiar with manually building Docker images to circumvent this bug. Is there documentation on how to go about doing this?

Please understand… this is a show-stopper for us!

martin.peeters · April 30, 2025, 11:45am

Hi!

The bug has just been resolved by our team.
It will be included in the next release.

GitHub pull request can be found here;

github.com/openremote/openremote

UI Fix: Insights can now be opened without authentication again

openremote:master ← openremote:bugfix/unauthorized-insights

opened 08:41AM - 30 Apr 25 UTC

MartinaeyNL

+12 -7

### Description Fixes #1770 This PR includes a fix for the standalone Insigh…ts web app, where unauthenticated access was throwing exceptions. The Insights app is accessible without a user login, since dashboards can be distributed publicly. Due to recent changes with the localization (updating user language in Keycloak), the Insights app produced 403 errors because they were not logged in. Now, the "keycloak user language" related logic is skipped when not logged in. ### Changelog - Now skipping GET `/user/user` in Insights custom app when unauthenticated. - Fix for `core` attempting to update user language (in Keycloak) when not being logged in. Now skipping this step. - Fix for `core` requesting user language (from Keycloak) when not being logged in. Now skipping this step. ### Checklist - [ ] 1. Acceptance criteria of the linked issue(s) are met - [ ] 2. Reproduction steps in the linked issue are tested and verified. (both locally, and on a deployment) - [ ] 3. Changes are manually tested by you and the reviewer

abra · May 12, 2025, 1:18pm

Although this bug has been resolved, we are still waiting for the next release…

When is the next release expected?