Patrick Zimmer |
Home | Projects | Music | Sitemap | Contact |
Sws DemonstrationProjects / Academic / Sws Demonstration Here it is shown that the Login Use case operates as expected. The login screen contains the SWS logo (Figure 1a) and username/password entry fields (Figure 1b). ![]() ![]() Figure 1a ---------------Figure 1b Username (â??ug98060â?) and password (â??passwordâ?) are entered (Figure 1c) and the Login option chosen (Figure 1d). ![]() ![]() Figure 1c ---------------Figure 1d The following parameter values are included with the login request: username=ug98069 passKey=11*12*0*2*9*6*7*8 If username and password values match a database entry then the â??Login Successâ? card (Figure 1e) is returned. Otherwise an error message is returned prompting re-entry of username and password (Figure 1f). ![]() ![]() Figure 1e ---------------Figure 1f Upload Here it is shown that the Upload Use case operates as expected. The requirement is that a text file with the specified name and content be created in the users home directory. From the â??Login Successâ? card (Figure 2a) the options to Browse and Upload are available (Figure 1b) ![]() ![]() Figure 2a ---------------Figure 2b The â??Uploadâ? card contains Filename and Message entry fields (Figure 1c). The Message entered is of the form shown in Figure 2d. ![]() ![]() Figure 2c ---- ----------Figure 2d With Filename and Message entered (Figure 2e) the Upload option is chosen (Figure 2f). ![]() ![]() Figure 2e ------------ --Figure 2f The following parameter values are included with the upload request: username=ug98069 sessionKey= 0.3687345424273414 filename=Test data=7*0*1*1*53*51*44*55*50*42*26*24*30*15*50*5*11*12*22*55* 19*11*4*3*53*12*5*6*12*37*32*50*61*47*41*51*40*61*40*54* 49*54*34*48*38*35*42*46*48*44*48*41*47*57*41*43*52*56*36 A successful upload causes the filename (Figure 2g) and the encrypted message to be displayed (Figure 2h). ![]() ![]() Figure 2g --------------Figure 2h Browse Here it is shown that the Browse and Up Directory Use cases operate as expected. This allows flexible navigation through the directory structure. Choosing the Browse option (Figure 3a) a listing of viewable items in the home directory of user ug98069 is displayed (Figure 3b). ![]() ![]() Figure 3a----------------Figure 3b The following parameter values are included with the upload request: username=ug98069 sessionKey= 0.3687345424273414 path=/home/ug98069 Choosing a directory (DIR) option from the menu (Figure 3c) causes the contents of the directory to be displayed (Figure 3d). Request parameters remain unchanged except path: path=/home/ug98069/test ![]() ![]() Figure 3c --------------Figure 3d Choosing the UPDIR option from the menu (Figure 3e) causes the contents of the previous directory to be displayed (Figure 3f). ![]() ![]() Figure 3e ---------------Figure 3f Request parameters remain unchanged except path: path=/home/ug98069 View ![]() ![]() Figure 3g ---------------Figure 3h Request parameters remain unchanged except path: path=/home/ug98069/test.txt As shown the path variable successfully keeps track of the current location enabling simple navigation. It has also been shown that the uploaded message has been encrypted, uploaded and stored unencrypted in the appropriately named file on the server. The file content has then been re-encrypted, transmitted back to the phone, decrypted and displayed. As required the services demonstrate encrypted transmission in both directions between client and server. |
|
Home | Projects | Music | Sitemap | Contact |