Server Requirements for OMA Client Provisioning
4/8/2010
The following list shows server requirements for use of OMA Client Provisioning:
- The OMA Client Provisioning Server and WAP Push gateway must be included in the Operator trusted and secure network.
- The OMA Client Provisioning Server must support sending WBXML encoded WAP push message over WSP connectionless push sessions at port 2948.
- If the server supports over the air (OTA) bootstrap, meaning that the OEM enabled OTA bootstrap at time of manufacture, the OMA Client Provisioning Server must support the OTA message signed with both a network-specific shared secret and a user personal identification number (PIN). For more information about how to enable OTA bootstrap, see Enabling OTA Bootstrapping.
- The WAP push gateway OMA Client Provisioning Server used must be an Operator trusted gateway and must not allow routing message from outside of the trusted zone.
- If supporting OTA continuous provisioning over a WAP push, the WAP push gateway must authenticate the push initiator (OMA Client Provisioning Server). The WAP push gateway must also set the authentication flag in the Push-Flag header that is sent to the device in the push message.
- If the server supports configuring the APPLICATION characteristic for OMA Client Provisioning, it must use of OMA Client Provisioning version 1.1 XML.