Skip to content
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

[ERROR] permissions.json authorized_labels filter #20

Open
MartinCartajena opened this issue Oct 18, 2024 · 1 comment
Open

[ERROR] permissions.json authorized_labels filter #20

MartinCartajena opened this issue Oct 18, 2024 · 1 comment

Comments

@MartinCartajena
Copy link

Hello,

I have tested your configuration, and I am experiencing issues with the permissions.json file. If I define a label for one of the users who can access Orthanc, and then log in to Orthanc with that user, it only shows the studies that contain that label. The problem arises when accessing OHIF with the same user. It should only show the studies with that label, but instead, sometimes the request to fetch the studies returns a 403 error, and other times it retrieves the studies correctly. However, when trying to make a request for the series of those studies, the request returns an empty array of series, even though there are series for that study.

This only happens when a value other than "*" is added to the authorized_labels parameter in the permissions.json file.

  • permission.json and request with the error (with label):
    Captura de pantalla 2024-10-18 100231

console-403

  • permission.json and request without the error:
    image

image

I’m not sure if there might be any changes that need to be made to the OHIF requests to receive data filtered by labels. Any help is welcome.

@MartinCartajena MartinCartajena changed the title permission.josn authorized_labels error [ERROR] permissions.json authorized_labels filter Oct 18, 2024
@amazy
Copy link
Member

amazy commented Oct 18, 2024

Hi,

In our system, when you open OHIF, you open it with a resource token, not a user token; therefore, the call to look for prior studies is not authorized and this is something that we actually expect.

I'm quite surprised that this call sometimes succeeds since, with a resource token, it shall always be forbidden

Alain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants