This configuration works well for the default Orthanc UI, but I’m encountering issues with Orthanc Explorer 2 (OE2). When I check the network tab, I see the following error:
Your authorization web-service is not returning the response in the format the authorization plugin is expecting.
I know this is not really well documented - but, if you plan to make OE2 work with the auth-plugin, you must very likely implement something similar to this webservice.
Note that the legacy UI is not supposed to work together with the authorization plugin unless you provide a token argument in the url.
OE2 requires your webservice to implement “user permissions” such that OE2 can show/hide the accessible features in the UI.
HI Alain ,
so i have set up the keycloak and orthanc-auth-service container its running . got the message like “Got the public key from Keycloak” on orthanc-auth-service docker console…
then i hit http://localhost:8042/app/explorer.html but i am getting 403 error
in the docker console getting error like this
why its getting this error ?how exactly the keycloak flow ?
i have gone through the repo and reademe file several time…but i am not getting properly.
pls help
There might be a way to make a bridge between keycloak and your webapp but I actually don’t know much about Keycloak.
If your users are already logged in your app, you might probably just not need Keycloak and have the auth-service use the HTTP headers from your webapp and interface with your webapp instead of interfacing with Keycloak.
We actually never tried to make it work with dicom-json source since the dicom-web source is working fine. Any reason not to use the dicom-web source ?
I’ll add a TODO to support ohif-dicom-json but I can not commit on when this will be done.