Installing a Debug Token in your PlayBook

This note describes how to configure a PlayBook with a Debug Token so it can be used to install applications like TunnelTilt.

Steps Required

Let’s go through these in sequence

Request a Code Signing Key
Point your browser to  Provide the following information:

  • First Name and Last Name for requester
  • Company
  • Email address
  • Country
  • CSJPIN (to be used when using the Code Signing Keys)

You will get a quick response mail acknowledging the request ()

Some time after that (around 2 hours) you will get one or two emails (depending on whether you asked for BB, for PB, or for both) each with one CSJ attached ()

The CSJ files have a name of the form: client-PBDT-CLIENTNUMBER.csj (client-RDK-CLIENTNUMBER.csj for the BB) where CLIENTNUMBER identifies “you”, the author that requested the Code Signing Keys.

Next save the CSJ files somewhere:

bash-3.2$ pushd ~/Software/Keys/
~/Software/Keys /Developer/SDKs/Research In Motion/BlackBerry WebWorks SDK for TabletOS ~/tmp

bash-3.2$ ls

Register the Signer
Now register the signer with RIM using the blackberry-signer application.  You need the CSJPIN to use the keys, and you will create a local STOREPASSWORD for later.

bash-3.2$ blackberry-tablet-sdk/bin/blackberry-signer -register \
 -csjpin CSJPIN -storepass STOREPASSWORD \
~/Software/Keys/client-RDK-CLIENTNUMBER.csj  \
Info: CSK file created.
Info: Developer certificate created in /Users/epelegri/Library/Research In Motion/author.p12
Info: Successfully registered with server.
Info: Successfully registered with server.

Next you will get Emails indicating the CLIENTNUMBER was successfully registered with Signing Servers (ID RDK and/or ID PBDT) ()

We can now use this store to do multiple operations, including:

Create the Debug Token
The Debug Token is created specifically for a given PlayBook; you can get its DEVPIN from the Options panel, under About/Hardware.  We use the blackberry-debugtokenrequest application

bash-3.2$ blackberry-tablet-sdk/bin/blackberry-debugtokenrequest \
-storepass STOREPASSWORD -devicepin DEVPIN \
Info: Debug token created.

Put the PlayBook in Development Mode
Before actually installing the debug token, you need to set the PlayBook in Development Mode. That is under Options/Security. That will show the IP for your device and will also give you an opportunity to set the password. Note that your device may have more than one IP address, e.g. one for WiFi and one for USB, if connected physically that way.

  • Get the device IP (DEVICEIP)
  • Set and record the password for the device (DEVICEPASS)

Install the Debug Token
And finally we are ready to install the debug token. The PlayBook should (still) be in Development Mode, and connected with the same IP as above, now use the blackberry-deploy application as follows:

bash-3.2$ blackberry-tablet-sdk/bin/blackberry-deploy \
-installDebugToken ~/Software/Keys/ \
-device DEVICEIP -password DEVICEPASS
Info: Sending request: Install Debug Token
Info: Action: Install Debug Token
Info: File size: 2252

More links

About pelegri

Engineering, CloudBees
This entry was posted in PlayBook and tagged . Bookmark the permalink.

10 Responses to Installing a Debug Token in your PlayBook

  1. pelegri says:

    New link to a webapp that provides interactive help related to Code Signing –

  2. Pingback: Building Samples for AIR open source project and deploying to the BlackBerry Playbook | Open Source News

  3. Pingback: Hello NDK beta 2 – Step by Step | Open BB News

  4. Pingback: GamePlay 1.1 – New Features and Samples | Open BB News

  5. Pingback: Building and Deploying WebWorks Samples | Open BB News

  6. Pingback: DosBox – From GitHub to Your PlayBook | Open BB News

  7. Pingback: Belligerent Blocks – Using Scoreloop SDK on the PlayBook | Open BB News

  8. pelegri says:

    Also see Mark Sohm’s post on Code Signing at DevBlog:

  9. Pingback: Skia on PlayBook | Open BB News

  10. Russian Squirrel says:

    Hi, pelegri!
    In the official Blackberry’s tutorial there is a one more step:
    4. 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 registration files.
    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.
    $ blackberry-keytool -genkeypair -keystore
    -storepass -dname “cn=” -alias author

    But I allready got an author.p12 file after the step 3:
    $ blackberry-signer -register -csjpin

    Now I able to sign my apps with this author.p12 file, but failed with that created in step 4. And You didn’t cover this step in Your article as well.

    Can You explain please what this step for and do I need to create new cert with blackberry-keytool for the app signing purpose?

    Thank You.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s