Configure your computer to sign apps and create debug tokens
Before you begin: Request permission to sign applications by completing the BlackBerry code signing key web form. After your application is accepted, you receive two CSJ registration files by email—one for app signing, and one for creating debug tokens. You'll use these files to register with the RIM Signing Authority.
The following steps help you configure your computer to sign applications and create debug tokens. You should only perform these steps once.
You can find blackberry-signer and blackberry-keytool in the bin subfolder where you installed the BlackBerry SDK.
- On the command line, navigate to the bin subfolder where you installed the BlackBerry SDK.
- Configure your keystore to
communicate with the RIM Signing
Authority by using the blackberry-signer tool. The password you specify in the -cskpass parameter allows you to access the RIM Signing
Authority using your identity. You should protect the
blackberry-signer -csksetup -cskpass <create_a_password>If you already configured your keystore and registered your CSJ file, this command returns the following message:
CSK file already exists. Use -cskdelete to delete first.Do not use the cskdelete command line option unless you forgot your CSK password. If you forgot your CSK password and delete the CSK file, you need to request a new CSJ registration file. To request a new CSJ file, complete the BlackBerry code signing keys web form.
Register with the RIM Signing Authority using your CSJ registration files by using the blackberry-signer tool. In this step, you need to specify the registration PIN you entered in the PIN field on the web form when you requested permission to sign applications. If you connect to the Internet through a proxy server, you must specify additional command line options to contact the RIM Signing Authority (See Configure application signing through a proxy server).
blackberry-signer -register -csjpin <PIN> -storepass <csk password from step 1> <RDK_CSJFile> <PBDT_CSJFile>
This value instructs the tool to request that the RIM Signing Authority associate your RIM Development Key (RDK) CSJ file with you public key.
This value specifies the registration PIN that you specified when you requested your code signing key.
This value specifies the password for your keystore. You should protect this password.
This value specifies the path to your RIM Development Key (RDK) CSJ file.
This value specifies the path to your PlayBook debug token (PBDT) CSJ file.
- Create a Developer Certificate
by using the blackberry-keytool tool. Ensure that the
common name (company name) parameter matches the name submitted when you requested the CSJ
The following command creates a Developer Certificate in the file named output_file.p12. The password you specify in the -storepass parameter allows you to use the .p12 file to sign BAR files. You should protect the .p12 file and its password.
blackberry-keytool -genkeypair -keystore <output_file.p12> -storepass <create_a_password> -dname "cn=<company_name>" -alias author
Configure application signing through a proxy server
During the signing process, your computer connects to the RIM Signing Authority. If your computer connects to the Internet through a proxy server, you should append the options in the following table to your blackberry-signer and blackberry-debugtokenrequest commands.
This option specifies the network host that provides the proxy service. The host parameter can be an IP address or a fully qualified domain name.
This option specifies the port number on your proxy server through which blackberry-signer or blackberry-debugtokenrequest should communicate with the RIM Signing Authority.
This option allows you to provide your user name if your proxy server requires authentication.
This option allows you to provide your password if your proxy server requires authentication.
Example: blackberry-signer command line
blackberry-signer -proxyhost 192.168.1.1 -proxyport 80 -register -csjpin <PIN> -storepass <KeystorePassword> <RDK_CSJFile> <PBDT_CSJFile>