Mobile Phone Client
Contents
Mobile Phone Client 2.x
Overview
Swivel Mobile Phone 2.x apps are named Mobile Phone Client 2.0, the Swivlet referring explicitly to the Java Mobile Phone Client
The PINsafe Mobile Phone Client 2.x allows the storage of 99 security strings to be stored on the phone. The PIN is not stored on the phone. Requesting a top up from the PINsafe server resets all the security strings on the mobile phone, providing 99 security strings for authentication. The value of 99 security strings is fixed and cannot be changed. You can use the device to get one-time codes for PINsafe login and PIN change.
Each Mobile Phone Client can be configured automatically using a SSD server and is provisioned with a unique Mobile Provision Code which provides information about the Mobile Phone Client that only allows a specific user on a specific mobile phone to request the security strings.
For the PINsafe Android Client see Android 2.0
For the Blackberry 10 client see Blackberry 2.0
For the iPhone select IPhone 2.0.
For the Windows Mobile version select Windows Phone(8) 2.0 How To Guide.
For the Windows Phone 7 and Blackberry 6 the previous version will still exist and be used for these models, see Blackberry.
Integrating with the Mobile App
Integration of login portals is usually straight forward with Mobile Apps, although if TURing and Pinpad images are used, then these should not be automatically generated as a login will be expected using those methods.
Mobile Phone Client 1.0
Overview
Swivel Mobile phone apps are named Mobile Phone Client, the Swivlet referring explicitly to the Java Mobile Phone Client
The PINsafe Mobile Phone Client allows the storage of 99 security strings to be stored on the phone. The PIN is not stored on the phone. Requesting a top up from the PINsafe server resets all the security strings on the mobile phone, providing 99 security strings for authentication. The value of 99 security strings is fixed and cannot be changed. You can use the device to get one-time codes for PINsafe login and PIN change.
Each Mobile Phone Client can be configured automatically using a SSD server and is provisioned with a unique Mobile Provision Code which provides information about the Mobile Phone Client that only allows a specific user on a specific mobile phone to request the security strings.
For the PINsafe Android Client see Android
For the Blackberry client see Blackberry
For the iPhone select IPhone.
For the Java applet for Java enabled phones see Swivlet How To Guide
For the Windows Mobile version select Windows Mobile How To Guide.
For the Windows Phone 7 version select Windows Phone 7 How To Guide.
Integrating with the Mobile App
Integration of login portals is usually straight forward with Mobile Apps, although if TURing and Pinpad images are used, then these should not be automatically generated as a login will be expected using those methods.
