I've disabled TLS v1.0 and 1.1 within Healthshare setting, but still seeing these error messages when running a security scan. We do have apache being used. What else can I try?
My team is working on redesigning and implementing an Ensemble production on Red Hat OpenShift Container Platform. We had to learn about Kubernetes and IKO.
I'm currently trying to find out how to have one Web Gateway route to multiple servers Management Portal. The only thing that I have come up with so far is to potentially make different routes per server?
I have a development, test, and production server and I want to use the same Gateway server using IIS to do SSL/TLS encryption for the CSP pages.
I have a .woff2 file I'm trying to serve over CSP.
If I set: ^%SYS("CSP","DefaultFileCharset")="UTF8"
Then it "just works" - but I'd rather not do something so heavy-handed/instance-wide, on principle. (This is for something that will ultimately be published on the Open Exchange.)
After what is seemed was weeks, I finally got SSL/TLS enabled on both Apache Web Server and IRIS using the Web Gateway. However while we can now use HTTPS to connect to our Development instance of IRIS, I am running into several errors when I have others try to access the Management Portal via HTTPS.
I am not sure if this is the correct place for this question, but I am struggling to setup TLS security for our IRIS Management Portal and etc. through Apache and the Web Gateway. I have a couple of questions when it comes to the setup.
if I build a private key and certificate within Red Hat, does that certificate have to be on everyone's pc to connect to the Management Portal?
Can I use a self signed Certificate?
Can I use the existing CA on the server, or do I need to work with my Data Security team to get a Certificate?
I've configured IRIS/HealthConnect with an external web server to support TLS encryption. It's installed on the same server as IRIS, but is a different instance and version of Apache httpd. That all works as expected.
I would also like to keep the "private" web server available, but I'm having an issue with using the fully-qualified domain name in the URL vs. just the hostname itself.
If I use http://servername:52773/csp/sys/UtilHome.csp to log on, all is well.
On this webinar, we’ll demo AtScale, InterSystems Reports (Logi), IRIS BI, IRIS NLP and answer the questions on how to develop, build, and deploy Analytics applications using InterSystems IRIS.
Date & Time: Monday, August 23 — 10:00 AM EDT
Speakers: 🗣 @Carmen Logue, InterSystems Product Manager - Analytics and AI 🗣 @Evgeny Shvarov, InterSystems Developer Ecosystem Manager
In the WRC, we frequently see customers contact us because their Web Gateway is unable to serve web pages. This article will explain a frequent reason why these errors can occur, and explain some tools which can be used to debug the problem. This explanation is focused on the Web Gateway serving InterSystems IRIS instances, but the same explanation should apply to the CSP Gateway serving Caché instances as well.
In the WRC, we often see customers raise questions regarding a new Web Gateway setup where the Management Portal half-loads, but doesn’t show images. This article will explain why this error occurs, as well as how to fix it. This explanation is focused on the Web Gateway serving InterSystems IRIS instances, but the same explanation should apply to the CSP Gateway serving Caché instances as well.
Most server-client communication on the web is based on a request and response structure. The client sends a request to the server and the server responds to this request. The WebSocket protocol provides a two-way channel of communication between a server and client, allowing servers to send messages to clients without first receiving a request. For more information on the WebSocket protocol and its implementation in InterSystems IRIS, see the links below.
I've configured my Ensemble instance to use IIS 7, according to the instructions CSP Gateway configuration Guide and I've configure the CSP Virtual application.
We tested REST Services as described for Caché DocServer example and for requests using http protocol it works without problems. However when we use the https protocol for the same REST Service it is not available. Our infrastructure is as follows: Apache with openssl, which works on the other hand well for CSP with https. If we switch on the web gateway http trace facility we could see the request of CSP pages by https://... but again a request of a REST Service by https:// will not result in a entry in the tracer. We hope that this description of the problem is understandable.
By date.png)
Open Exchange app.png)
