Securing Data Change Notifications

If you use data change notifications (DCN) to notify Unwired Server of EIS changes, secure the communication stream to avoid packet sniffing or data tampering. Use Sybase Control Center to configure the DCN stream after you have created SSL certificates.

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.