I have just configured a Osirix Lite on my Mac at home and tried to connect to a test instance built running on AWS/Win 2016. It’s all plain-vanilla out-of-the-box Orthanc config.
Without the authentication WADO works just fine from Osirix Lite but with Authentication ON on the Orthanc side returns un- status of 401.
Manually accessing Orthanc Explorer (…8042/app/explorer.html) and the WADO URL (/8042/?..) from a Chrome works OK including the authentication.
Before I invest more time into this, first I want to ask if anyone has seen this behavior, and hopefully there is a workaround or something I have missed in the config to fix this.
I am guessing that there is a difference in how Osirix tries to authenticate and how Orthanc does it (like Basic Digest etc.)
If not, I go dive deeper into it, so I want to know if I need to so as well.
Thanks!
Manabu Tokunaga
WinguMD, Inc.