Error ‘This type is not supported’ when using Deepnet mobile id
Posted by on 13 August 2014 09:01 AM

After upgrading to iOS 7, the token used on MobileID does not work and the 2X Client is unable to authenticate the user.

Versions affected

2XRemote Application Server all versions


The cause of the problem is that iOS 7 changes the behaviour of an API that MobileID calls to acquire the phone's device ID. As a security measure, to prevent users' tokens from being copied or stolen, MobileID locks the user's token to the user's phone device by encrypting the token data with the device's hardware ID. Unfortunately, iOS unexpectedly changes the behaviour of the API that returns the device's hardware ID, which prevents MobileID from correctly decrypting the user's token data. Effectively, iOS 7 corrupts the existing token stored by MobileID in the phone.


There is no way that MobileID can automatically recover the corrupted token, unfortunately, as there is no back door built into MobileID. Users who upgrade to iOS 7 will have to remove the corrupted token and reinstall the token. Please note that the MobileID app itself does not need to be removed and reinstalled. It is the user's token that has to be removed and reinstalled.

(2 vote(s))
Not helpful

Comments (0)
Post a new comment
Full Name: