Archived:Certain EAP types not supported in OMA Client Provisioning (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}}.
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
Compatibility
Platform(s): S60 3rd Edition
Article
Created: User:Technical writer 1
(31 Oct 2007)
Last edited: hamishwillee
(07 Sep 2012)
Description
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.
Solution
Currently there is no solution available. This is expected to be fixed in future releases.
(no comments yet)