-
Notifications
You must be signed in to change notification settings - Fork 43
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
Add token authentication option for DICOMweb #1349
Conversation
3b51045
to
9b1d9e8
Compare
I converted this back to a draft because I realized we are not actually passing this token-containing session to However, |
9b1d9e8
to
7f0856a
Compare
This now works again, but it depends on imi-bigpicture/wsidicom#117 |
As of the latest `wsidicom` release (0.13.0), the new `__init__` method just takes a `requests.Session` object. The old `__init__` method was moved to the class method `create_client()`. So we need to update the way we initialize it. In girder#1349, we are adding authentication where we create the DICOMwebClient object ourselves, so go ahead and do that now to simplify that one. Signed-off-by: Patrick Avery <[email protected]>
As of the latest `wsidicom` release (0.13.0), the new `__init__` method just takes a `DICOMwebClient` object. The old `__init__` method was moved to the class method `create_client()`. So we need to update the way we initialize it. In girder#1349, we are adding authentication where we create the DICOMwebClient object ourselves, so go ahead and do that now to simplify that one. Signed-off-by: Patrick Avery <[email protected]>
As of the latest `wsidicom` release (0.13.0), the new `__init__` method just takes a `DICOMwebClient` object. The old `__init__` method was moved to the class method `create_client()`. So we need to update the way we initialize it. In girder#1349, we are adding authentication where we create the DICOMwebClient object ourselves, so go ahead and do that now to simplify that one. Signed-off-by: Patrick Avery <[email protected]>
9d91994
to
e6df8d8
Compare
When the user is creating a DICOMweb assetstore, if they select the "token" authentication type, an input box will appear where the user must enter the token. This token is saved in MongoDB, and is used for making all requests for this DICOMweb assetstore. That includes requests for importing the data (which may only be done by an admin), and requests for viewing the data (which may be done by anyone with access to the folder). If an admin wishes to restrict users from viewing DICOMweb assets that were imported using this token, the admin must restrict access to the imported items via girder's folder access controls. Signed-off-by: Patrick Avery <[email protected]>
This is what it was before... Signed-off-by: Patrick Avery <[email protected]>
The `WsiDicomWebClient` class now takes a `DICOMwebClient` object as its argument. Update our instantiation to reflect this. Signed-off-by: Patrick Avery <[email protected]>
e6df8d8
to
6f165e1
Compare
Signed-off-by: Patrick Avery <[email protected]>
When the user is creating a DICOMweb assetstore, if they select the "token" authentication type, an input box will appear where the user must enter the token.
This token is saved in MongoDB, and is used for making all requests for this DICOMweb assetstore. That includes requests for importing the data (which may only be done by an admin), and requests for viewing the data (which may be done by anyone with access to the folder).
If an admin wishes to restrict users from viewing DICOMweb assets that were imported using this token, the admin must restrict access to the imported items via girder's folder access controls.
Fixes: #1313
Depends on: imi-bigpicture/wsidicom#117