•
SigKey
: The name of each signature key (.csi) file. Use the following naming conventions for the keys:
client-RRT-*.csi, client-RBB-*.csi, client-RCR-*.csi.
•
Dhttp.proxyHost
: The name or IP address of the proxy server.
•
Dhttp.proxyPort
: The proxy server port number if you do not specify 80 as the default port number.
3.
Repeat step 2 for each .csi file that you want to register.
Sign an application using a proxy server
Your registration key and .csk file are stored together. If you lose the registration key or the .csk file, you cannot request code
signatures. If you are not an ISV partner, contact your ISV Technical Partnership Manager. If you are a non ISV partner, send an
email message to [email protected].
1.
At the command prompt, navigate to the BlackBerry® Signature Tool bin directory. For example:
C:\Program Files\Research In Motion\BlackBerry JDE 4.6.0\bin
2.
Type
Java -jar -Dhttp.proxyHost=myproxy.com -Dhttp.proxyPort=80 SignatureTool.jar
3.
In the File Selection window, select the .cod file(s) to sign.
4.
Click
Open
.
View the signature status for an application
For files that are not signed, the
Status
column contains
Failed
. The Web Signer might have rejected the .cod file because the
private key password was typed incorrectly.
1.
Start the BlackBerry® Signature Tool.
2.
Select a .cod file.
3.
View the
Status
column.
For files the Web Signer has signed, the
Status
column contains
Signed
.
Using keys to protect APIs and data
To create an internal key pair to use with an internal signing authority system, or an external key pair to use with an external
signing authority system, you must apply protection to sensitive APIs, protect data in the runtime store, and protect data in a
persistent object.
The RSAE.key is an external key, and ACMI.key is an internal key.
Development Guide
Sign an application using a proxy server
84