You
can secure two EIS operations: data change notifications (DCN) and push (notifications). To
completely secure DCNs, you must protect the communication channel as well as authorize the
event request being made on Unwired Server.
Depending on your environment, you can secure one or both EIS
notification type. Implementations are seperated to allow you configure securtiy so that
technical user is authorized for DCN event changes, but not for Push, and another
technical user is authorized for Push events, but not DCN.
- DCN – (Not applicable to Online Data Proxy) only Enabling Authorization of
DCNs is a required activity for securing this notification. By
default, DCN shares the same certificate and HTTPS listener is
Unwired Server and this secure stream is already
enabled. You only need to change this default configuration if your
environment needs to implement a unique security profile to meet your
organization's stringency requirements. If you need to understand how the
DCN feature is implemented and monitored across
Unwired Platform, review the contents listed in
Implementation of Data Change Notification.
These topics help you find DCN related information across the documentation
set.
- Push – operations allow the EIS to send a notification to
synchronize data directly to a specific device. It is entirely separate from
MBO operations that can also use notification to trigger synchronization.
Push events are secured the same way as DCN. Tasks that describe a DCN
activity can be used to secure Push notification events.