viewON page asks for web authentication despite anonymous read-only access enabled - Printable Version +- Ewon Technical Forum (https://techforum.ewon.biz) +-- Forum: Development (https://techforum.ewon.biz/forum-50.html) +--- Forum: Custom Web Pages/viewON/Talk2M Visualization (https://techforum.ewon.biz/forum-55.html) +--- Thread: viewON page asks for web authentication despite anonymous read-only access enabled (/thread-2737.html) |
viewON page asks for web authentication despite anonymous read-only access enabled - itstomis - 03-04-2025 An existing client asked that I remove the web login for their very simple viewON virtual HMI. However, the page still asks for a login when viewing the page with the Alarm History widget on it. The page is just the Alarm History Widget, basically nothing else. In the Ewon setup (Setup -> Main -> General -> Identification), Anonymous read-only access is enabled for Alarm History ($dtAH). In fact, I checked all text boxes just to check, and it still asks for authentication. If I enter login info, it displays the page. If I cancel out of entering login info, it still populates the widget, but then displays the red error messages: Quote:Failed to read tag values! And then it kicks me back to my Home viewON page after a few seconds. RE: viewON page asks for web authentication despite anonymous read-only access enabled - itstomis - 28-05-2025 Bump, can any Support comment? RE: viewON page asks for web authentication despite anonymous read-only access enabled - AngelaT - 29-05-2025 What firmware version are you running? It is working for me in 14.9s4 with a view that only has the alarm history widget. Are you sure there's nothing else on the view? /rcgi.bin/vows/readVars doesn't seem like the call viewON would make to get the alarm history. Is there any javascript that tries to get or set some values behind the scenes or something like that? RE: viewON page asks for web authentication despite anonymous read-only access enabled - itstomis - 09-06-2025 I seem to have solved it, although I don't understand the what's going on. The problem wasn't being caused by the Alarm History Widget itself, it was being caused by the page being empty?!? If I delete the Alarm History Page and replace it with an exact duplicate of my Home page (call it Home2) (or with a copy of my Trends page), it works fine. But then if I delete all the elements from the Home2, leaving as just an empty page with a title bar, side navigation buttons, and a Time & Date, it gives me the error. So to solve it at least temporarily, I put a single tiny text box with a single process value behind the Alarm History Widget, and now it works. (29-05-2025, 07:08 PM)AngelaT Wrote: What firmware version are you running? It is working for me in 14.9s4 with a view that only has the alarm history widget. I'm also on firmware 14.9s4 I don't believe there's any javascript running in the background? I don't recall setting anything up. I described my bandaid solution above. I've attached a version of my project with info about the client scrubbed, for reference. You can see that on the "AlHist" page, there's a tiny text box referencing the "WW_Level" variable. The existence of this text box on the page seems to stop the error from popping up. example bug.zip (Size: 31,95 KB / Downloads: 3) RE: viewON page asks for web authentication despite anonymous read-only access enabled - AngelaT - 10-06-2025 This might actually be caused by your date field. Your date field is animated with BASIC code and running BASIC code requires a login. I ran into this on one of my projects. I ended up working around it by creating a string tag to hold the date. Then I had a basic script that updated that tag once a minute (and removed the seconds field so no one knew it wasn't updating every second). RE: viewON page asks for web authentication despite anonymous read-only access enabled - itstomis - 10-06-2025 But that doesn't explain why my pages DON'T require authentication as soon as there's a single tag reference somewhere on each one of them. If the problem was just that the Date field requiring BASIC (which requires login), then shouldn't *all* my pages require login? |