Weasis cannot show images with dcm4chee 5.24.0 ONLY secured UI

[VFX]

Hello,

When I click eye icon, it can open Weasis. 

However, it does not have images. 

Weasis 3.7.1

dcm4chee 5.24.0 ONLY secured UI

Keycloak 10.0.0

Wildfly 19.1.0

I set Property in Web Application

IID_STUDY_URL=weasis://$dicom:rs --url "{{qidoBaseURL}}{{qidoBasePath}}" -r "studyUID={{studyUID}}" --query-ext "&includedefaults=false" -H "Authorization: Bearer {{access_token}}"

IID_PATIENT_URL=weasis://$dicom:rs --url "{{qidoBaseURL}}{{qidoBasePath}}" -r "patientID={{patientID}}" --query-ext "&includedefaults=false" -H "Authorization: Bearer {{access_token}}"

I also tried this.

ID_STUDY_URL=weasis://$dicom:rs --url "{{qidoBaseURL}}{{qidoBasePath}}" -r "studyUID={{studyUID}}" --query-ext "&includedefaults=false"

IID_PATIENT_URL=weasis://$dicom:rs --url "{{qidoBaseURL}}{{qidoBasePath}}" -r "patientID={{patientID}}" --query-ext "&includedefaults=false"

I also try to deploy below

weasis.war

weasis-ext.war

weasis-pacs-connector.war

They do not work.

How can I set dcm4chee 5.24.0 with secured Ui version to work with Weasis?

Thank you

[Todd Jensen]

I've had a similar issue with 5.23.1 with secured DICOMweb access but only with Weasis on Windows. It works on macOS. Try enabling DEBUG and rolling logs in Weasis and then look at the Weasis log files. It seems to not be using the access token correctly on Windows as it is redirected to the Keycloak login page.

My Weasis log:

23.09.2021 15:34:52.669 *DEBUG* [Dicom Model-pool-1-thread-1] org.weasis.dicom.explorer.rs.RsQueryResult: QIDO-RS request: https://REDACTED/rs/studies?0020000D=1.3.6.1.4.1.5962.1.2.8.20040826185059.5457&includefield=00080020,00080030,00080050,00080061,00080090,00081030,00100010,00100020,00100021,00100030,00100040,0020000D,00200010&includedefaults=false

23.09.2021 15:34:54.427

 *ERROR* [Dicom Model-pool-1-thread-1] org.weasis.dicom.explorer.rs.RsQueryResult: QIDO-RS with studyUID 1.3.6.1.4.1.5962.1.2.8.20040826185059.5457 javax.json.stream.JsonParsingException: Unexpected char 60 at (line no=1, column no=1, offset=0)

at org.glassfish.json.JsonTokenizer.unexpectedChar(JsonTokenizer.java:577) 

at org.glassfish.json.JsonTokenizer.nextToken(JsonTokenizer.java:394) 

at org.glassfish.json.JsonParserImpl$NoneContext.getNextEvent(JsonParserImpl.java:402)

Server logs show the token is not being sent or accepted as the Weasis request is redirected:

65.29.178.241 - - [23/Sep/2021:20:42:15 +0000] "GET /REDACTED/rs/studies?0020000D=1.3.6.1.4.1.5962.1.2.8.20040826185059.5457&includefield=00080020,00080030,00080050,00080061,00080090,00081030,00100010,00100020,00100021,00100030,00100040,0020000D,00200010&includedefaults=false HTTP/1.1" 302 1086 "-" "Weasis/3.7.1 (Windows 10; 10.0; amd64; default; NATIVE) Java/16.0.1" 

65.29.178.241 - - [23/Sep/2021:20:42:16 +0000] "GET /auth/realms/dcm4che/protocol/openid-connect/auth?REDACTED&redirect_uri=http%3A%2F%2FREDACTED%2Frs%2Fstudies%3F0020000D%3D1.3.6.1.4.1.5962.1.2.8.20040826185059.5457%26includefield%3D00080020%2C00080030%2C00080050%2C00080061%2C00080090%2C00081030%2C00100010%2C00100020%2C00100021%2C00100030%2C00100040%2C0020000D%2C00200010%26includedefaults%3Dfalse%26auth_callback%3D1&scope=openid&response_type=code HTTP/1.1" 200 3025 "-" "Weasis/3.7.1 (Windows 10; 10.0; amd64; default; NATIVE) Java/16.0.1"

Todd Jensen, PhD

Jensen Informatics LLC

[Nicolas Roduit]

Yes, the problem is related to the length of the token which is cut by IE and Chrome only under Windows. With Firefox on Windows it should work.

The same problem existed on kheops (https://demo.kheops.online) which uses Keycloack and dcm4chee. It has been fixed by using a shorter token on Keycloack.

There are also modifications in development in Weasis to make it fully compatible with Open ID Connect. So the token won't be passed through the Weasis URI anymore.

1) Weasis => dcm4chee (implemented in Weasis 3.7.1)
2) dcm4chee => Weasis (should be in Weasis 3.8.0)