Securing DCNs

The most efficient way to update data from the back-end datasource is to allow the EIS to “push” data changes to Unwired Server. This is accomplished with data change notifications (DCN). DCN can operate over HTTP, however, for a secure communication, use HTTPS and ensure the EIS and Unwired Server use basic authentication.

1. Preparing SSL Certificates for DCNs
   DCN, which uses HTTP Basic authentication, uses a Base64-encoded username:password field that can be intercepted by network sniffers. Encrypt DCN communications and always use HTTPS to send DCNs. HTTPS requires the DCN sender import the Unwired Server certificate (or that of its CA signer) into its local equivalent of a truststore.
2. Creating and Enabling a DCN Security Profile
   An administrator must enable and configure the HTTPS port for DCN connections as part of a security profile so that developers can construct callouts from the EIS backend to send Unwired Server data change notification (DCN) requests.
3. Enabling Authorization for Data Change Notification CDB Insertions
   (Not applicable to Online Data Proxy) All DCN requests are authorized by checking if the user making the request is in the “SUP DCN User” role within the security configuration of the request’s target package.