Namespaces

Variants
Actions

Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

Archived:Enforcing terminal security policy changes for a device (Known Issue)

From Wiki
Jump to: navigation, search

Archived.pngArchived: 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
S60 3rd Edition (initial release)
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.

See also

OMA Device Management DDF for Terminal Security (v1.3)

This page was last modified on 7 September 2012, at 06:59.
37 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×