Permissibility of Database Changes for Start, Resume, TimedTrigger, and Notification Service

Use

In general, the database may only be changed if ensured that the action was carried out by the user and not "foisted" onto the user. A method for "foisting" requests is referred to as Cross Site Request Forgery (XSRF).

Due to the architecture of the World Wide Web, it is not possible to determine whether a start request or resume request for an application originated from a user and not from an XSRF attack. For this reason, the application may not change the state of the server during this request.

This also applies to actions triggered by the TimedTrigger and notification service if the TimedTrigger or notification service is not activated by a user action but immediately when the application starts or resumes.

All actions executed by the user are protected against XSRF by the Web Dynpro Framework. This means it is not possible to foist the button click onto the user.