-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When OHIF is configured with OIDC after auth it redirects to callbackurl again, another refresh works #2850
Comments
Hey @smithago , thanks for the report. Can you try |
Will do @sedghi . How do I access v3-stable? I have only seen you release the entire source code and containers. I assume sync to that branch and generate the files and try. |
I just tried, looks like lot of steps have changed in that branch. Here is what I was doing to generate index.html and minified and webpacked index.umd.js.* cd platform/viewer Looks like the build:package is missing and the webpack.commonjs.js |
you don't need to |
Where do you upload the content? This doc page might be helpful https://v3-docs.ohif.org/deployment/build-for-production/ |
I upload the content to Azure Blob container with static website enabled. The build has changed in v3, I am not able to produce the same minified and merged content. Can someone help me? |
The built get separated into chunks, but still if you get index.html and main javascript bundle generated it knows each chunk path and load them as necessary. Can you send me an email at [email protected] , we can setup a meeting to fix this |
@jbocce ditto |
We just release the OHIF 3.8, you can find more details here https://ohif.org/release-notes/3p8/ |
Bug Report
Describe the Bug
OHIF viewer is configured with OIDC properties to support authenticated access to backend service.
After the auth redirections and confirmation, ohif redirects to callbackurl.
Refreshing the base url works.
What steps can we follow to reproduce the bug?
We have a github repo on how to configure ohif viewer to Azure DICOM service and deploy ohif viewer as a static website in storage account.
https://github.com/microsoft/dicom-ohif
It has step by step instructions on how to set it up.
If you follow this and authenticate, you will run into the final stage of redirection to callbackurl.
It is also mentioned as a github issue from one of our customers
microsoft/dicom-ohif#7
The text was updated successfully, but these errors were encountered: