WebTerminal not working with HealthConnect 2025.1

Question

Question

Neil Thaiss · Oct 28

Hi,

I have just installed WebTerminal on my local instance of Health Connect 2025.1, but it does not work and returns a HTTP 401 error.

Can any one help, as I have never installed WebTerminal before?

Has there been any changes in Health Connect to stop it working in version 2025.1?

Thanks.

Neil

Product version: HealthShare 2025.1

$ZV: IRIS for Windows (x86-64) 2025.1 (Build 230_2U) Wed Jun 4 2025 18:49:31 EDT

Discussion (11)3

Log in or sign up to continue

Thomas Wuppermann · Nov 13

Same here.
Since there is an open issue on Github https://github.com/intersystems-community/webterminal/issues/158 and the maintainer states that it's not being actively maintained, I assume there is no easy fix?

0 0

score 0 · Answer 1 · 2025-10-28T12:00:35-04:00

HTTP 401 means "Unauthorized" check that the web application /terminal has the correct credentials and correct authentication methods (password, LDAP etc.)
(the /terminalsocket should be always unauthenticated, its the default)
to help you resolve this, you may use auditing, to see if there is a "login failure" when you try to access.

score 0 · Answer 2 · 2025-11-06T06:59:56-05:00

It's definitely a login issue as I'm not always prompted to login or provide any credentials.
I have no idea why I don't always get a login prompt, but when I do WebTerminal does work.

score 0 · Answer 3 · 2025-11-13T07:06:10-05:00

Credentials are not requested, as most likely your existing session has not expired yet.
By default, the timeout is 1 hour (see the "WebTerminal.Engine:WSKEYEXPIRES" class parameter).

score 0 · Answer 4 · 2025-10-28T13:24:58-04:00

Another challenge is to enable WebSocket protocol on your webserver
I just had the "pleasure" to do this for IIS 👺
It's not a default

score 0 · Answer 5 · 2025-11-06T07:03:59-05:00

Yes, I had enable WebSocket protocol on IIS, but when I use IIS, rather than InterSystems Private Web Server (PWS) I get a 404 error, rather than 401.
I'm trying this on two different instances, one using the PWS and one using IIS, with different errors, 401 or 404.

score 1 · Answer 6 · 2025-11-13T07:19:18-05:00

I will assume that you are using "Normal" (in which the user _SYSTEM is turned off) or even "Locked Down" (the user "UnknownUser" has no roles at all): Initial User Security Settings^DOC

I'm using "Locked Down", IRIS 2025.2CE and ran into a lot of different bugs when using WebTerminal v4.9.5:

<PROTECT>endSession+25^%SYS.cspServer
<LICENSE LIMIT EXCEEDED>
etc.

Fortunately, the WebTerminal source code is available for analysis and editing.

The problem can be solved in two ways: either fix the source code or add the missing role. I chose the latter.

In my case, it is enough for the web application /terminalsocket to add the %Admin_Secure role in addition to the existing roles. After that, it doesn't hurt to clean up all existing sessions:

kill ^WebTerminal("AuthUser")

If the <LICENSE LIMIT EXCEEDED> error persists after this, restart the IRIS instance.

PS: Advisory for IRISSECURITY in InterSystems IRIS 2025.2

score 1 · Answer 7 · 2025-11-13T11:37:41-05:00

Looks similar to at least part of the issue I covered in https://community.intersystems.com/post/webterminal-broken-iris-20242

score 0 · Answer 8 · 2025-11-13T18:23:51-05:00

Dmitry Maslennikov · Nov 13

could you try iterm, how is it working?
https://openexchange.intersystems.com/package/iterm

0 0

score 0 · Answer 9 · 2025-11-13T21:15:57-05:00

@Dmitry Maslennikov do you intend to address any of the 5 open issues on the iTerm repo, one of which is IMO a significant security vulnerability I reported more than a year ago?

score 1 · Answer 10 · 2025-11-13T22:49:49-05:00

ahh, yes, I'll try to have a look
with so many projects on my hands quite easy to get distracted, and since it's an open-source project not easy to find a time to properly maintain them