Skip to content

Unsecured Archive Non TLS

Vrinda edited this page Mar 27, 2023 · 1 revision

Starting with version 5.16.2, Target URL and Keycloak Server ID are no longer supported in RS Forward Rule child object. These 2 attributes are now replaced with a Web Application Name. This Web Application shall be configured on a different archive (which may be present in a different cluster).

Configuration

One may either

  • create a LDIF file (e.g.):

      version: 1
      dn: cn=RS Forward,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
      objectClass: dcmRSForwardRule
      cn: RS Forward
      dcmWebAppName: archive2WebApp
      dcmRSOperation: CreatePatient
      dcmRSOperation: UpdatePatient
      dcmRSOperation: DeletePatient
      -
      
      dn: cn=http,dicomDeviceName=dcm4chee-arc2,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
      objectClass: dcmNetworkConnection
      objectClass: dicomNetworkConnection
      dicomHostname: localhost
      cn: http
      dcmProtocol: HTTP
      dicomPort: 8780
      -
      
      dn: dcmWebAppName=archive2WebApp,dicomDeviceName=dcm4chee-arc2,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
      objectClass: dcmWebApp
      dcmWebAppName: archive2WebApp
      dcmWebServiceClass: DCM4CHEE_ARC_AET
      dcmWebServicePath: /dcm4chee-arc/aets/DCM4CHEE/rs
      dicomNetworkConnectionReference: cn=http,dicomDeviceName=dcm4chee-arc2,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
      -
    

    and import it to the LDAP Server by using the ldapmodify command line utility.

  • or use the New Entry... function of Apache Directory Studio to add rule on Device Level (e.g.: dicomDeviceName=dcm4chee-arc) or on Application Entity Level (e.g: dicomAETitle=DCM4CHEE) of the Archive Configuration. Subsequently one may use Add Attribute... and Add Value... functions of Apache Directory Studio to add attributes on the rule level

Note :

  • The dicomHostname and dicomPort shall be adapted to the values used in your Wildfly configuration for Archive 2.
  • In the above example of LDAP configuration for this feature, only 3 of the RESTful services are included. One may add multiple services as per one's application needs. For the other options which can be added one may refer to the link given below.

One may refer to RESTful Forward Rule
and Web Application to understand the description of attributes and also has the complete list of supported RESTful operations supported by this feature in archive.

Go to the Control tab on Configuration page in archive UI and reload the configuration.

Clone this wiki locally