OHIF + Keycloak but wihtout docker

Support
1

I was following the instructions to setup OHIF + keycloak on this page: User Account Control | OHIF. After installation of the OHIF I can load main page “/” but
when going to /pacs or /pacs-admin parts of the OHIF installation I am getting error “JavaScript not activated”. After reviewing the documentation I noticed that there is “docker-compose up” command executed in .recipes directory. Is there a way to activate JavaScript on above mentioned paths without running docker commands? Or is there any documentation of running OHIF as standalone application without docker?

Thank you!

2

Yeah, you can clone the ohif viewer from the offical github repo, install packages with yarn install and run with yarn start. There is a readme in the repository.
Then you can implement your own auth, or let it without any.

3

Hi matheusrdk,
Thank you for information but I did installation as you mentioned without success. The /pacs and /pacs-admin are giving the error that JavaScript is not activated hence my request for help. Main page (static content - “/” ) is loading without issues.

Is there anything else that I can do to fix the problem?

4

As far as I know, the ohif viewer 3.x dont have any /pacs or /pacs-admin page. This pages refer to the pacs server, witch in this case ir Orthanc (can be Dcm4Chee too, or any other). You are following the docker tutorials, that build an image of the viewer, pacs and keycloak, each one prepared for the other, like this /pacs page that is made to access the orthanc instance you created with docker.

5

That doc is really outdated, i’m recreating a recipe with nginx, oauth2proxy and keycloak this week or the next week

6

We recently added several recipes for implementing authentication with Keycloak in OHIF. You can find them here:

7

Thank you Alireza for this information, appreciated!

I tried that on three different servers (local - macos, remote - redhat 9, ubuntu 22) without success, not sure why is not working. It seems that installation (docker) finishes properly. I have proper access to KeyCloak and can login as admin only, but everything else gives me 500 Server Error. I found the error when running the docker that Oauth2 container can not start due to wrong ip adderss 127.0.0.11 ? I searched all settings looking for this ip address but without success. .Do you have any additional pointers on how to solve this?

8

I have the same problem, I tried several versions, cento7, AlmaLinux… and I get several 500 errors… I saw the tutorial several times and I review all the code, it is exactly the same but I get that 500 error.

9

It is really weird, we haven’t really changed anything on this