Archived:Enforcing terminal security policy changes for a device (Known Issue)
Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.
Article Metadata
Tested with
Devices(s): Nokia E61i
Compatibility
Platform(s): S60 3rd Edition
Article
Created: User:Technical writer 1
(12 May 2009)
Last edited: hamishwillee
(07 Sep 2012)
Description
The Terminal Security Device Description File (DDF) can be used to manage the device lock. The initial device lock policy can be set when the user enters the lock code. However, when the security policy is subsequently changed, the change is not reflected on the device (on S60 3rd Edition).
Solution
To make sure that the new policy is enforced on the device immediately and correctly, a policy "lock code has expired" needs to be sent. After this, the lock code expiry time must be set to -1 which will enforce user to enter a new lock code.
Wdsknowledge2 - OMA Device Management DDFs for Symbian^3/Anna
Hi Hamish
Are there any updated OMA DM DDF and security policy files for Symbian^3/, Anna and Belle?
Thankswdsknowledge2 12:56, 18 November 2011 (EET)
Hamishwillee - Wdsknowledge2 - not as far as I know
For the terminal policy, this was updated to v1.3 a couple of days ago (link above fixed). This is for all devices following and including S60 3rd edition. I can't find any update to the "general" security policy document which is archived. I don't know enough about OMA DM to know if there is overlap from this document. Suggest you request on discussion boards to get more eyes on the problem.
Regards
Hamishhamishwillee 04:51, 21 November 2011 (EET)