Motorola MC3090G Integration Guide - Page 113

Installing Certificates, Device Management Security, Remote API Security

Page 113 highlights

Application Deployment for Mobile 6.1 5 - 3 Installing Certificates Use XML provisioning to query and delete certificates from certificate stores. To add a new certificate the Privileged Execution Trust Certificate Store, use the following sample provisioning document: To create your own provisioning document with real certificate information: 1. Obtain a certificate from a security provider such as VeriSign. 2. Double-click on the certificate file (.CER) to open it. 3. Click on the Details tab and locate the Thumbprint field. 4. Copy the contents of the Thumbprint field and replace the value in the XML example above. 5. Click the Copy to File... button. 6. Click Next to start the Certificate Export Wizard. 7. Select Base-64 encoded X.509 (.CER) and then click Next. 8. Set the File Name to CertOutput.xml and click Next. 9. Click Finish to export the certificate. 10. Open the exported file, CertOutput.xml, in a text editor (i.e., NotePad). 11. Copy the contents of the file (excluding the first line, last line, and CR/LF) and replace the value of the "EncodedCertificate" parameter in the xml example above. Device Management Security You can control access to certain device settings and security levels, such as installing applications and changing security settings. Refer to the Windows Mobile Version 6 Help file for information on device management security. Remote API Security The Remote API (RAPI) enables applications that run on a desktop to perform actions on a remote device. RAPI provides the ability to manipulate the file system on the remote device, including the creation and deletion of files and directories. By default, Motorola ships with RAPI in the restricted mode. Certain tools, such as RAPIConfig,

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236

Application Deployment for Mobile 6.1
5 - 3
Installing Certificates
Use XML provisioning to query and delete certificates from certificate stores. To add a new certificate the Privileged
Execution Trust Certificate Store, use the following sample provisioning document:
<wap-provisioningdoc>
<characteristic type= “CertificateStore”>
<characteristic type= “Privileged Execution Trust Authorities”>
<characteristic type= “657141E12FA45786F6A57CA6464032D4B3A55475”>
<parm name= “EncodedCertificate” value= “
This is sample text. This is sample text. This is sample text. This is sample text.
This is sample text. This is sample text. This is sample text. This is sample text.
This is sample text. This is sample text. This is sample text. This is sample text. = “/>
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>
To create your own provisioning document with real certificate information:
1.
Obtain a certificate from a security provider such as VeriSign.
2.
Double-click on the certificate file (.CER) to open it.
3.
Click on the
Details
tab and locate the
Thumbprint
field.
4.
Copy the contents of the
Thumbprint
field and replace the value in the XML example above.
5.
Click the
Copy to File…
button.
6.
Click
Next
to start the Certificate Export Wizard.
7.
Select
Base-64 encoded X.509 (.CER)
and then click
Next
.
8.
Set the File Name to CertOutput.xml and click
Next
.
9.
Click
Finish
to export the certificate.
10.
Open the exported file, CertOutput.xml, in a text editor (i.e., NotePad).
11.
Copy the contents of the file (excluding the first line, last line, and CR/LF) and replace the value of the
“EncodedCertificate”
parameter in the xml example above.
Device Management Security
You can control access to certain device settings and security levels, such as installing applications and changing
security settings. Refer to the
Windows Mobile Version 6 Help
file for information on device management security.
Remote API Security
The Remote API (RAPI) enables applications that run on a desktop to perform actions on a remote device. RAPI
provides the ability to manipulate the file system on the remote device, including the creation and deletion of files
and directories. By default, Motorola ships with RAPI in the restricted mode. Certain tools, such as RAPIConfig,