Personal tools
You are here: Home → support → WiKID Strong Authentication System Issue Tracker → Unable to unlock the iPhone client after two successful starts

#7 — Unable to unlock the iPhone client after two successful starts

State Resolved
Version:
—
Area iPhone Software Token
Issue type Bug
Severity Medium
Submitted by (anonymous)
Submitted on May 07, 2009
Responsible
—
Target release: 3.x
Return to tracker
Last modified on Jun 17, 2009 by admin
You set it up and it works fine
You close and log back in and it works
You close the 3rd time and it says your passphrase is invalid

OS: 2.2.1
Steps to reproduce:
You set it up and it works fine
You close and log back in and it works
You close the 3rd time and it says your passphrase is invalid
Added by admin on May 07, 2009 12:02 PM
Issue state: Unconfirmed → Confirmed
This is only being reported in some users.
Added by admin on May 07, 2009 12:55 PM
Issue state: Confirmed → In progress
: Just go in enter you passphrase
: when you hit the domain part close
: uh oh
: if I do a full passcode generate everytime it stops giving errors
: there it is
: yeah totally broken for me now too
: its corrupting the passphrase or something if you dont fully run the app
: But if you generate a passcode it never fails
: ah. if you run a passcode request i bet it re-encrypts the token so all is happy. and if you don't, something happens that the token gets corrupted
: just a guess. never seen the source for the iphone client so i can only guess
 i know the way the regular token works, when you get a valid passcode reply, it updates the token file because the passcode TTL might have changed... assuming the iphone client works the same way, that's very likely the cause
Added by admin on May 18, 2009 09:52 AM
Issue state: In progress → Resolved
Should be resolved, but requires testing. Apple just released the update today.
Added by admin on May 25, 2009 08:23 AM
Issue state: Resolved → Confirmed
Added by admin on May 25, 2009 08:24 AM
Target release: None → 3.x
This issue is still unresolved.
Added by (anonymous) on Jun 03, 2009 01:11 AM
A new version, 3.0.2, has just been submitted to the App Store that enables some debug functionality that can be sent to WiKID Support for troubleshooting.

Once the app is approved (should be in a week or so):

To enable, go to the "Settings" app, then "WiKID Token Client", "Advanced", then turn "Debug mode" to "ON". Then go back into the WiKID client and do whatever trips the error. If the app crashes out, re-launch it. Go to the front screen, click on the (i) in the top left of the status bar to get to the About screen. There should be a button at the bottom that says "Send Log to Dev Team". This will send us the log (then truncate it so it doesn't fill up your phone's filesystem). You can then disable Debug mode, since that will have an impact on performance.
Added by ghaygood on Jun 08, 2009 10:29 PM
Issue state: Confirmed → Resolved
A new version, 3.1, has just been submitted to the App Store that fixes the way the iphone client handles the padding. I implemented a not-so-great (okay, a sucky) algorithm that caused these problems. I re-wrote it and have successfully connected to all the domains that were previously exhibiting this issue.

I don't know how quickly Apple will approve this update, so stay tuned.

Add response