Gazelle Proxy is under renovation. We firstly focused on the backend and more particularly on the management of the channels and forwarding of messages. That is to say that Gazelle Proxy 6.0.0 comes with a brandnew technology stack for those two features. Although it does not change deeply the use of the tool, changes have been performed and are listed below.

Support of TLS 1.3

The tool administrator can now enable the support of TLSv1.3. The following cipher suites are available:

• TLS_AES_256_GCM_SHA384
• TLS_AES_128_GCM_SHA256
• TLS_CHACHA20_POLY1305_SHA256

The configuration is performed from Administration > Secured channel management

HTTP Rewrite

Gazelle Proxy is now able to rewrite part of the HTTP Header so servers can properly route the received messages based on the Host header present in the message. 

Gazelle Test Management 8.0.0 is a big step in the renovation of Gazelle. The management of the users (excluding the management of the organizations for now) is performed outside of Gazelle Test Management. It also brings improvements to comply with European General Data Protection Regulation (GDPR) and improve the security of passwords.

A new login screen is available

Note that the Gazelle logo has changed. It will be integrated in the Gazelle applications as they are renovated.

What does it mean?

You have created your account under Gazelle Test Management 7.1.6 or prior: at next loging you will be asked

Who has access to Rocket.chat

Rocket.chat at https://chat.ihe-catalyst.net has been set up for both the IHE Joint Connectathon 2022 and the Swiss EPR Projectathon 2022. All the users who are registered participants or monitors for those events have an account in rocket.chat.

As a participant, we mean that a badge for one of those events has been requested and paid.

Login with your Gazelle TM credentials

Rocket.chat is integrated with Gazelle TM user database. Accounts for the IHE Joint Connectathon 2022 participants have been created with random passwords. We do not want you to use the 'direct' login feature in rocket.chat. On the contrary, you shall use the SSO feature provided by Keycloak.

How to ?

1. Access Rocket.chat at https://chat.ihe-catalyst.net

2. Click "Click here to login with Gazelle Test Management credentials" button

A pop-up opens, fill out the form with your Gazelle username and password

Gazelle Test Management 6.6.0 is out !

This new release of Gazelle Test Management:

Allows you to quickly see the status of your network configuration [Read more];

Offers a new user interface for the testing dashboard [Read more].

Statistics about your SUTs' network configuration

Gazelle Test Management offers a feature for the systems under test to share the connectivity details of their network interfaces. Templates are generated by the tool based on the capabilities selected for each of your systems under test. 

Before the testing event starts, you are expected to review those network interfaces and make sure the details match your implementation:

Below is a few tips so that you can quickly find the pages you are used to work on in Gazelle Test Management:

Dear colleagues,

On behalf of Gazelle team, we wish you a wonderful New Year.

It is still time to apply for being a monitor at the next European Connectathon.

This year, the event will be held at Den Haag (The Netherlands) from April, 16th to April, 20th.

May you be interested in joining the amazing monitor team, fill out the application form at https://gazelle.ihe.net/content/monitor-recruitment-form-hague-2018

You will need an account on Gazelle website to access this form; if you do not have one yet, contact either Hilary or Anne-Gaëlle.

Best regards

The release of Patient Manager (9.8.0) published today and available at https://gazelle.ihe.net/PatientManager now supports FHIR DSTU3 and has been updated to be compliants with the latest version of the PDQm and PIXm supplements.

Dear all,

Gazelle team is pleased to announce the release of the Jboss7 version of Order Manager, available from now on at https://gazelle.ihe.net/OrderManager.

Please note that the location of the tool has changed and all HL7 and DICOM services are now reachable at IP address: 164.132.1.36.

In addition to the new graphical layout, here are some new features which might be of interest:

IHE Academia in the Netherlands organizes an IHE XDS advance training course. We still have some place available in the training so hurry up to register.

More information on the program and how to register at : http://iheacademy.nl/en/node/26/details/20150119113605000936

I have received this request a couple of time and thus I have decided to post a blog in order to explain how to do it. 

Hapi provides a test panel app that allows a user to easily use the library in order to send or receive HL7 messages. That GUI provides a check box for using TLS.

The IHE ATNA profile requires mutual authentication, this means that the client AND the server need to provide a certificate in order to reach successful TLS negociation. Checking the TLS box does not tell hapi which certificate to use. 

What most people are forgetting is that they need to configure Java to tell what certificate to use when initiating the TLS communication and what certificate to trust. In order words, the user who would like to use TLS, needs to provide java with the pointer to the truststore (list of certificate to trust) and the pointer to the keystore (certificate to use to initiate TLS).

The easiest way to do it without breaking the entire java installation is to provide some arguments to the call to java.