Zurück
-
Titel
After updating the Defender iToken to the latest version, receive error, "Invalid Token. Token is locked to a different device." -
Beschreibung
In certain circumstances after upgrading the Defender Soft Token to version 1.1 or 1.2 on iPhone, users are receiving an error when opening the app and the token will no longer generate response codes
"Invalid Token. Token is locked to a different device."
This does not seem to affect devices were the iToken application was manually updated rather than automatically updated.
-
Ursache
In certain circumstances Apple's 'identifierForVendor' attribute may change unexpectedly on the device, this results in the Defender iToken showing as locked.
-
Lösung
STATUS:
The latest version of the Defender iToken 1.3 is now available from the Apple App Store fixing this issue.
WORKAROUND:
If the user has downloaded the iToken 1.1/1.2 version from the App Store when it was previously available, a admin can re-program a new token in Active Directory using the Defender 5.7 MMC console and activate it on the affected device.
More information on programming the iToken is available below:
Programming an iToken
NOTE: This workaround DOES NOT appear to work for iTokens programmed using the 5.6.x version of the Defender MMC. The latest 5.7 MMC console is available for download from Defender - Download New Releases. Alternatively, version 1.3, when released, will allow new tokens to be programmed from Defender 5.6.
NOTE: This issue is only with Apple'ss iOS only. Other token types, i.e. Android, etc., are not affected. -
Änderungsanforderung
474661, 473507