Access control based on Archive AEs - dcm4che/dcm4chee-arc-light GitHub Wiki

This feature can be used when the use case is such that there are multiple Application Entities which need to store objects to a central archive, but one Application Entity should not be able to see the studies sent by the other Application Entities.

The feature can be explained/configured in two parts :

• Store Access Control
• Access Control

• storescu simulating the external object source (e.g. modality) STORESCU, from which objects are being received.

1. For Store Access Control : Configured on AE

• Store study1 to archive using storescu tool as shown below

    storescu -c DCM4CHEE1@localhost:11112 /path_to_study1.dcm
  

• Store study2 to archive using storescu tool as shown below

    storescu -c DCM4CHEE2@localhost:11112 /path_to_study2.dcm
  

• Go to archive UI Navigation page -> Studies tab and select DCM4CHEE in the Web Applications dropdown and query studies, one will notice that only study1 is seen, but not study2. Similarly, select DCM4CHEE2 in the Web Applications dropdown and query studies, one will notice that only study2 is seen, but not study1.

2. For Store Access Control : Configured using Rule

• Store study having InstitutionName as InstitutionAny to archive using storescu tool as shown below

    storescu -c DCM4CHEE@localhost:11112 /path_to_study.dcm
  

• Store study3 having InstitutionName as InstitutionMain to archive using storescu tool as shown below

    storescu -c DCM4CHEE3@localhost:11112 /path_to_study3.dcm
  

• Go to archive UI Navigation page -> Studies tab and select DCM4CHEE in the Web Applications dropdown and query
  studies, one will notice that only study is seen, but not study3. Similarly, select DCM4CHEE3 in the Web Applications dropdown and query studies, one will notice that only study3 is seen, but not study.

3. For any other study where Store Access Control is not configured by any of the two ways described; but only Access Control ID is configured (refer section 3 in Access Control Configuration using LDAP),

• Store study4 to archive using storescu tool as shown below

    storescu -c DCM4CHEE@localhost:11112 /path_to_study4.dcm
  

• Go to archive UI Navigation page -> Studies tab and select DCM4CHEE in the Web Applications dropdown and query studies, one will notice that only study4 is seen.