|Applies To||Software token 3.0 for Blackberry|
|Issue||Is it possible to deploy software token 3.0 to a Blackberry with content protection enabled?|
Deploying software token 3.0 to Blackberry devices with content protection enabled
|Resolution||Deploying a token to the BlackBerry device with Content Protection enabled has been tested using the SPHelper component. The Device contacted SPH and SPH pushed a token to the device. The token was successfully imported.|
Deploying a token was also tested using the normal command line PushToken Utility. When Content Protection was enabled on the device, a token was pushed to the device and the token was successfully imported.
|Workaround||Content protection is enabled on blackberry device. The device is protected with a password to prevent the access by others.|
|Notes||Content Protection for the BlackBerry is a setting on the Device that allows the End User to effectively set a password for their device. If the device is not tied to a BES, or the BES admin does not lock a device. Content Protection will enable a single user to lock their device if not in use. If this setting is turned "On" on the device, the BES admin cannot re-set the password for that device to unlock it or change it. If the End User forgets the password, or it is entered in incorrectly 10 times the device is disabled.|
Content Protection is a separate, independent feature that will not interfere with SecurID as it is a password lock for the entire device. If Content Protection is enabled on the device it will not prevent the RSA token Application from working.
|Legacy Article ID||a40801|