Mobile UniOTP Solution: Difference between revisions

From SecuTech Wiki
Jump to navigationJump to search
No edit summary
Joseph (talk | contribs)
No edit summary
Line 2: Line 2:
[[Category:UniOTP Mobile Solution]]
[[Category:UniOTP Mobile Solution]]


== Mobile UniOTP First launch and Settings ==
== Mobile UniOTP First Launch and Configuration ==


{| cellspacing="0" cellpadding="0" border="0" width=""
{| cellspacing="0" cellpadding="0" border="0" width=""
Line 8: Line 8:
| width="50" |  '''1'''  
| width="50" |  '''1'''  
| width="400" |  
| width="400" |  
<p>This is the screen you  will  see  the first time you use Mobile UniOTP.</p>
<p>This is the screen shown the first time the Mobile UniOTP application is lauched.</p>
<p>At this step, you must set the password to access the application.</p>
<p>At this step, you must set the password needed to access the application.</p>
<p>Fill in the fields [Password] and [Confirm password] and click  the [Confirm] button.</p>
<p>Fill in the fields [Password] and [Confirm Password] and tap the [Confirm] button.</p>
<p> The next time you  will  launch  the application, this password will be requested. </p>
<p>The next time the application is launched, this password will be requested.</p>
<p> If you forgot the password, please delete and reinstall the application on your device. In  this case, you will need to synchronize  your One Time Password application with the server once again. </p>
<p>If you forgot this password, delete and reinstall the application on your device. If this is the case, you will need to resynchronize your One Time Password application with the server.</p>
| [[Image:mobotp img01.jpg|270px]]<br><br>
| [[Image:mobotp img01.jpg|270px]]<br><br>
|-
|-
| width="50" | &nbsp;'''2'''  
| width="50" | &nbsp;'''2'''  
| width="400" | <p>Once  you  have  finished  setting up  your password, you will be redirected automatically to the main screen. </p>
| width="400" | <p>After setting the application password, you will be redirected automatically to the main screen.</p>
<p>From the main screen, please  click [Synchronize] at the bottom of the screen to access to the synchronization interface.</p>
<p>From the main screen, tap [Synchronize] at the bottom of the screen to access to the synchronization interface.</p>
| [[Image:mobotp img02.jpg|270px]]<br><br>
| [[Image:mobotp img02.jpg|270px]]<br><br>
|-
|-
| width="50" | &nbsp;'''3'''  
| width="50" | &nbsp;'''3'''  
| width="400" | <p>Please  choose  the type of One Time Password you  want  to  use  from the synchronization interface. You can choose  
| width="400" | <p>Select the type of One Time Password from the synchronization interface. You can choose  
among [Event-Based] [Time-Based] and [Challenge/Response].</p>
among [Event-Based], [Time-Based] and [Challenge/Response].</p>
<p>Depending on the type of OTP chosen, information needed for synchronization is different. Please  communicate to your administrator the information displayed on the screen.</p>
<p>Depending on the type of OTP chosen, information needed for synchronization is different. For reasons of security, Mobile UniOTP operates independently from use of network communication. Hence, please communicate to your administrator the information displayed on the screen.</p>
<p>
<p>
As  Mobile UniOTP won’t  connect  to the network  to send  information.  You  should tell  your administrator  this  information directly or through mail/phone.
If you decide to use Mobile UniOTP with OTP MGS, you will need a token file. Please send your synchronization information to support@esecutech.com to receive the token file corresponding to your device within 24 hours.
</p>
</p>
<p>
<p>
If  you  decide  to  use  Mobile  UniOTP  with OTP  MGS,  you  will  need  to  have  a  token file.  Please  send  your  synchronization information  to  support@esecutech.com  to get  the  token  file  corresponding  to  your
If you decide to use UniOTP API (included in UniOTP SDK), the information displayed here can be used directly.
device. We will give you an answer within 24 hours.
</p>
<p>
If you decide to use UniOTP API (included in UniOTP SDK), you can use directly this information.  
</p>
</p>
| [[Image:mobotp img03.jpg|270px]]<br><br>
| [[Image:mobotp img03.jpg|270px]]<br><br>
|-
|-
| width="50" | &nbsp;'''4'''  
| width="50" | &nbsp;'''4'''  
| width="400" | <p>Once information communicated to your administrator, click  the  [Synchronize] button to apply changes.</p>
| width="400" | <p>Once information has been communicated to your administrator, tap [Synchronize] to apply changes.</p>
<p>If you go back to the main screen without clicking  the  button, synchronization information will not be changed  and you will not be able to use  the  One Time Password. Make  sure to push  the [Synchronize] button  before going  back  to the main screen.</p>
<p>If returning to the main screen without synchronizing, synchronization information will not be saved and the application will not be able to generate correct One Time Passwords. Be sure to tap [Synchronize] before returning to the main screen.</p>
<p>A message will be displayed if the synchronization succeeded.</p>
<p>A message will be displayed if the synchronization succeeded.</p>
<p>Every time you open the Synchronization interface, new synchronization information is generated,  but it  is only saved if you  click  the [Synchronize] button. </p>
<p>Every time you open the Synchronization interface, new synchronization information is generated but is only saved if the [Synchronize] button tapped.</p>
| [[Image:mobotp img04.jpg|270px]]<br><br>
| [[Image:mobotp img04.jpg|270px]]<br><br>
|-
|-
| width="50" | &nbsp;'''5'''  
| width="50" | &nbsp;'''5'''  
| width="400" |  
| width="400" |  
<p>Once back to the main screen, choose  the icon corresponding to your type of OTP in order  to access to the OTP generation interface.</p>
<p>Once back to the main screen, tap the icon corresponding to your type of generated OTP to access to the OTP generation interface.</p>
| [[Image:mobotp img05.jpg|270px]]<br><br>
| [[Image:mobotp img05.jpg|270px]]<br><br>
|}
|}


== Event-Based ==
== Event-Based OTP Generation==


{| cellspacing="0" cellpadding="0" border="0" width=""
{| cellspacing="0" cellpadding="0" border="0" width=""
|-
|-
| width="50" | &nbsp;'''5'''  
| width="50" | &nbsp;''''''  
| width="400" |  
| width="400" |  
<p>Every  time you  access  the Event-Based OTP generation interface, a new password will be automatically generated.</p>
<p>Each time the Event-Based OTP generation interface is accessed, a new password is automatically generated.</p>
<p>If you are already on this screen, you can push  the  [Generate] button in  order  to generate a new password.</p>
<p>The [Generate] button can be tapped to generate a new password.</p>
<p>''Note: If you switch back and forth between the main screen and this screen, or if you push the button too many times, the OTP may get  desynchronized and need to be synchronized again.''</p>
<p>''Note: If you switch back and forth between the main screen and OTP generation screen, or if you generate a new OTP excessively in a short period of time, the OTP application may become desynchronized and would need to be synchronized again.''</p>
| [[Image:mobotp img06.jpg|270px]]<br><br>
| [[Image:mobotp img06.jpg|270px]]<br><br>
|}
|}


== Time-Based OTP ==
== Time-Based OTP Generation ==


{| cellspacing="0" cellpadding="0" border="0" width=""
{| cellspacing="0" cellpadding="0" border="0" width=""
|-
|-
| width="50" | &nbsp;'''5'''  
| width="50" | &nbsp;''''''  
| width="400" |  
| width="400" |  
<p>A  new password is generated automatically  every 60 seconds. Even  if you go  back  to  the main  screen  and  come back  to  this  interface, if 60 seconds have not passed, the password won’t change. </p>
<p>In the time-based OTP generation interface, a new password is generated every 60 seconds. Users cannot force the generation of a new password. For every time-based password generated, if 60 seconds have not lapsed, the password will remain the same, and thus only every 60 seconds is a new password generated.</p>
<p>There  is no  way  for  the  user  to  urge  the generation of a new password. </p>
<p>''Note: If the device time desynchronizes from the server time more than permitted, the device may get desynchronized. Please take note of this Make sure to not change the time of your device after you have synchronized it with the server.''</p>
<p>''Note: If the device time get  desynchronized from the server time more than it  is allowed, the device may get desynchronized. Make sure to not change the time of your device after you have synchronized it with the server. ''</p>
| [[Image:mobotp img07.jpg|270px]]<br><br>
| [[Image:mobotp img07.jpg|270px]]<br><br>
|}
|}


== Challenge/Response ==
== Challenge/Response Password Generation ==


{| cellspacing="0" cellpadding="0" border="0" width=""
{| cellspacing="0" cellpadding="0" border="0" width=""
|-
|-
| width="50" | &nbsp;'''1'''  
| width="50" | &nbsp;''''''  
| width="400" |  
| width="400" |  
<p>In order to generate a OTP, you must first input the challenge code received from the server. </p>
<p>In order to generate a OTP using the Challenge and Response system, input of challenge code received from the server is required. Authentication will be determined by the correct response generated from the given challenge.</p>
<br>'''Example of Use:'''<br>  
<br>'''Example of Use:'''<br>  
<p>After the  user logged in  the  website, the server will display a challenge code to the user and  asks  to input the corresponding OTP for  this code. The user inputs the challenge code on  this  interface to calculate the correct OTP. In this way, we can even  strengthen  the authentication process security.</p>
<p>After a user has logged onto a website, the server will display a challenge code to the user, requesting the user to input the corresponding OTP generated from this code. The user inputs the challenge code in the Challenge/Response interface to generate a OTP. This generated response is used to authenticate to the server and, hence, only the correct response can be used to successfully authenticate.</p>
| [[Image:mobotp img08.jpg|270px]]<br><br>
| [[Image:mobotp img08.jpg|270px]]<br><br>
|}
|}


== Other settings ==
== Other Settings ==


<p>From the [Settings] screen, you can perform operations listed below.</p>
<p>From the [Settings] screen, you can perform operations listed below.</p>
* Change password to  access  the application  
* Change the password for accessing the application
* Show the S/N(Serial Number)
* Display the S/N (Serial Number)
* Show the device time
* Display the device time  


[[Image:mobotp img09.jpg|270px]]
[[Image:mobotp img09.jpg|270px]]
[[Image:mobotp img10.jpg|270px]]
[[Image:mobotp img10.jpg|270px]]

Revision as of 12:55, 29 May 2012


Mobile UniOTP First Launch and Configuration

 1

This is the screen shown the first time the Mobile UniOTP application is lauched.

At this step, you must set the password needed to access the application.

Fill in the fields [Password] and [Confirm Password] and tap the [Confirm] button.

The next time the application is launched, this password will be requested.

If you forgot this password, delete and reinstall the application on your device. If this is the case, you will need to resynchronize your One Time Password application with the server.



 2

After setting the application password, you will be redirected automatically to the main screen.

From the main screen, tap [Synchronize] at the bottom of the screen to access to the synchronization interface.



 3

Select the type of One Time Password from the synchronization interface. You can choose among [Event-Based], [Time-Based] and [Challenge/Response].

Depending on the type of OTP chosen, information needed for synchronization is different. For reasons of security, Mobile UniOTP operates independently from use of network communication. Hence, please communicate to your administrator the information displayed on the screen.

If you decide to use Mobile UniOTP with OTP MGS, you will need a token file. Please send your synchronization information to support@esecutech.com to receive the token file corresponding to your device within 24 hours.

If you decide to use UniOTP API (included in UniOTP SDK), the information displayed here can be used directly.



 4

Once information has been communicated to your administrator, tap [Synchronize] to apply changes.

If returning to the main screen without synchronizing, synchronization information will not be saved and the application will not be able to generate correct One Time Passwords. Be sure to tap [Synchronize] before returning to the main screen.

A message will be displayed if the synchronization succeeded.

Every time you open the Synchronization interface, new synchronization information is generated but is only saved if the [Synchronize] button tapped.



 5

Once back to the main screen, tap the icon corresponding to your type of generated OTP to access to the OTP generation interface.



Event-Based OTP Generation

 '

Each time the Event-Based OTP generation interface is accessed, a new password is automatically generated.

The [Generate] button can be tapped to generate a new password.

Note: If you switch back and forth between the main screen and OTP generation screen, or if you generate a new OTP excessively in a short period of time, the OTP application may become desynchronized and would need to be synchronized again.



Time-Based OTP Generation

 '

In the time-based OTP generation interface, a new password is generated every 60 seconds. Users cannot force the generation of a new password. For every time-based password generated, if 60 seconds have not lapsed, the password will remain the same, and thus only every 60 seconds is a new password generated.

Note: If the device time desynchronizes from the server time more than permitted, the device may get desynchronized. Please take note of this Make sure to not change the time of your device after you have synchronized it with the server.



Challenge/Response Password Generation

 '

In order to generate a OTP using the Challenge and Response system, input of challenge code received from the server is required. Authentication will be determined by the correct response generated from the given challenge.


Example of Use:

After a user has logged onto a website, the server will display a challenge code to the user, requesting the user to input the corresponding OTP generated from this code. The user inputs the challenge code in the Challenge/Response interface to generate a OTP. This generated response is used to authenticate to the server and, hence, only the correct response can be used to successfully authenticate.



Other Settings

From the [Settings] screen, you can perform operations listed below.

  • Change the password for accessing the application
  • Display the S/N (Serial Number)
  • Display the device time