issue with token Authentication for ORTHANC

[holakunle]

hello

I want to appreciate the entire kitware team. great jobs guys.
however, most orthanc users using the orthanc with authentication cannot use volview and here is the major reason

Volview is yet to support passing a token in the URL (eg …/index.html?token=my-token) and that this token is included in every HTTP request sent by Volview to Orthanc.

Is there something that can be done?

[PaulHax]

That would be a great upgrade!

• VolView would need to read the token here: https://github.com/Kitware/VolView/blob/main/src/components/App.vue#L117
• Add the token to the file request from Orthanc, probably here: https://github.com/Kitware/VolView/blob/main/src/io/import/processors/downloadUrl.ts
• Test with Orthanc plugin
• Update Orthanc plugin

Do you know how the Orthanc plugin feeds VolView the file data?

Would you be intersted in helping with any of the other changes above?

[amazy]

Hi @PaulHax

Currently, Orthanc opens VolView with this kind of url: http://localhost:8042/volview/index.html?names=[archive.zip]&urls=[../studies/b601fd03-c389b0a6-8ce8d63f-f907e550-431323e1/archive] so it means there is actually a single query from VolView to Orthanc !

In both StoneViewer and OHIF, when we pass &token=my-token in the url, they end up adding this HTTP header to all requests sent to Orthanc:
Authorization: Bearer my-token

As soon as you have a patch in Volview, I can take care of testing it with Orthanc !

[floryst]

This is actually on my near-term plate, so I will be tackling this.

[floryst]

@amazy Support for token in the URL is now available in the main branch of VolView! Let me know if you have any issues or questions with it.

[PaulHax]

@amazy Any luck with testing the token URL parameter?

[amazy]

@floryst , @PaulHax I have tested it today and I confirm it works.

Thanks again !