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:Certain EAP types not supported in OMA Client Provisioning (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}}.

The different EAP (Extensible Authentication Protocol) types and especially combinations of them are not handled very well when using OMA Client Provisioning on S60 3rd Edition.

Article Metadata
Tested with
Devices(s): All 3rd Edition devices
Platform(s): S60 3rd Edition
S60 3rd Edition (initial release)
Created: User:Technical writer 1 (31 Oct 2007)
Last edited: hamishwillee (07 Sep 2012)


When using OMA Client Provisioning over SMS to provision S60 3rd Edition devices with settings like WLAN access points, certain EAP types, such as MSCHAPV2 (Microsoft Challenge Handshake Authentication Protocol) over PEAP (Protected Extensible Authentication Protocol), do not work.


Currently there is no solution available. This is expected to be fixed in future releases.

This page was last modified on 7 September 2012, at 06:54.
226 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.