design. develop. deploy.

Remote or Web Browser NX Application Token Request

This form generates a token request for your Production, Beta, or Development SmartSDK Web Browser NX or Remote Application.

Before You Start

Here's what you need before you can fill out this form an make a request.

1. Determine the type of token

The application we are generating a token for can be one of two types: Web Application, Remote Application. The tokens come in three flavours: Development, Production, Beta. Every application needs a Product ID, a unique identifier reserved by an organization and tracked by RiDP.

Application Type

You will need to specify which of the application types we should generate a token for:

  1. Web Application (an application deployed to a device and run via Web Browser NX)
  2. Remote Application (an application deployed to an external host)

Deployment Type

You'll need to specify if a token is to be generated for either Development or Production use. Development tokens can be used for app deployment to up to 20 devices, identified by device serial number. Production tokens are unrestricted, except for having an expiry date. RiDP can also provide Beta tokens, which are otherwise the same as production tokens, only with a 60-day expiry.

Please note: Production tokens require that the application passes a round compatibility testing before they can be issued.

2. Reserve a Product ID

A Product ID can be found in one of two ways:

  1. By fetching an existing Product ID already reserved for the application type, or
  2. By issuing a new Product ID Request for either a Remote or Web Browser NX SmartSDK Application Type.

Please note: Product IDs are tied to the application type. When reserving or re-using Product IDs those created for Web Applications can only be used to make Web Application tokens, and it is the same for Remote Application Product IDs.

3. Create a key pair

In order to have the public key required for this form, create a key pair (public and private keys). An easy way to do this is to leverage the material in AccessTokenSampleApp.zip or AccessTokenSampleApp2.zip (located in the Ricoh SmartSDK resource CD in the sample folder), running the following command:

java -jar AccessTokenSampleApp.jar -k

Please note: never share the private key generated with this command with any third-party, including RiDP. No Ricoh employee should ever ask for your private key.

Main Menu