cipality's scenario details. To be successfully authenticated to the application, using the cryptographic credentials associated to the application. The request creation and dispatching phase is depicted in the sequence diagram (see Figure 11.4). This phase starts with the creation of the m-Document that con- tains the service request. Specifically, the mobile user activates the mobile applica- tion and fills in the required fields in the predefined sequence of electronic forms (Step 1). When ending this process, the mobile application automatically creates an m-Document (Step 2). The secure mobile application digitally signs the m-Docu- ment (Step 3), using the cryptographic credentials associated with the operation of the mobile application and the specific user. If not, the process ends and has to be restarted from the first step (Step 1). The next step involves the creation of a request to the time-stamping authority, in order to obtain a valid time-stamp token. The mobile application automatically creates this request, while previously creates a hash value of the final m-Document. It attaches the hash value of the m-Document in this message (Step 4) and dis- patches it to the time-stamping authority (Step 5). The TSA processes the received request, issues a valid time-stamp token (Step 6), and responds to the mobile device with the signed and time-stamped hash value of the m-Document (Step 7). Once the m-Document has been digitally signed, the mobile application creates a SOAP message (Step 8) and embodies the signed document into it. In addition to what was last mentioned, the secure application embeds the required SAML authentication and authorization token for accessing the selected m-government service. The procedure that describes the way of obtaining a valid Service Delivery Platforms SWEB platform Mobile device Time-stamping authority 1: Fill the required fields of the electronic forms 2: m-document creation 3: Digital sign m-document 4: TSA request creation 5: TSA request dispatch 6: Creation of a va