Securing EIS Operations: DCN and Push

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 SAP Mobile 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 EIS Operations is a required activity for securing this notification. By default, DCN shares the same certificate and HTTPS listener is SAP Mobile 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 SAP Mobile Platform, review the contents listed in Implementing 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.

Securing DCN Communications
(Recommended for DCN environments only) By default, the installer automatically configures a single security profile for DCN communications with SAP Mobile Server and SAP Mobile Server administration communications with SAP Control Center. For most deployments, this default setup is sufficient; however, you can create a new security profile with new SSL certificates if you choose.
Enabling Authorization of EIS Operations
All EIS operations must be authorized before the event is processed. SAP Mobile Server authorizes these insertion events using either SUP DCN User or SUP Push User role and a security configuration that names the security provider that performs the authorization function.

Related concepts