comparison Sphinx/source/plugins/dicomweb.rst @ 665:9062c9c464f5

HttpHeaders in the definition of DICOMweb servers
author Sebastien Jodogne <s.jodogne@gmail.com>
date Thu, 29 Apr 2021 13:59:11 +0200
parents 324ca8f236b8
children d92edd545754
comparison
equal deleted inserted replaced
664:7fbe9147423f 665:9062c9c464f5
348 } 348 }
349 } 349 }
350 } 350 }
351 } 351 }
352 352
353 Finally, it is also possible to use client authentication with 353
354 hardware security modules and smart cards through `PKCS#11 354 The definition of a DICOMweb server can also specify the HTTP headers
355 to be provided during each request to the remote DICOMweb server. This
356 can for instance be useful to set authorization tokens::
357
358 {
359 [...]
360 "DicomWeb" : {
361 "Servers" : {
362 "sample" : {
363 "Url" : "http://localhost:8042/dicom-web/",
364 "HttpHeaders": {
365 "Authorization" : "Bearer HelloWorldToken"
366 }
367 }
368 }
369 }
370 }
371
372
373 Finally, it is possible to use client authentication with hardware
374 security modules and smart cards through `PKCS#11
355 <https://en.wikipedia.org/wiki/PKCS_11>`__ (this feature is only 375 <https://en.wikipedia.org/wiki/PKCS_11>`__ (this feature is only
356 available is the core of Orthanc was compiled with the 376 available is the core of Orthanc was compiled with the
357 ``-DENABLE_PKCS11=ON`` option in CMake, and if the Orthanc 377 ``-DENABLE_PKCS11=ON`` option in CMake, and if the Orthanc
358 configuration file has a proper ``Pkcs11`` section):: 378 configuration file has a proper ``Pkcs11`` section)::
359 379