Setting Up Authorization with a Technical User Role Stored in a Repository

Before any EIS event is submitted, the technical user mapped to either the SUP DCN User or SUP Push User role must be authorized by a security provider you define as part of a named security configuration.

1. Adding a Physical Technical User Role to Your Security Repository
   Often the DCN or Push user is not a real user in your security repository, but rather an artificial "technical" user whose credentials are simply a shared secret between the EIS developer writing the DCN client or Push code, and the platform administrator.
2. Updating an Existing Security Configuration for EIS Event Authorization
   Platform administrators create different security configurations to authenticate packages that are deployed to various domains. You can revise these existing security configurations to also authenticate EIS events.
3. Adding a New Provider to Authorize EIS Events
   Add an authorization provider used to authorize events for packages that use DCN or Push.
4. Mapping a SAP Mobile Platform Logical Role to a Technical User in a Repository
   Mapping the logical role binds it to another technical user's physical ID.