Hide Navigation Pane
Show Navigation Pane
Feedback
Download
SHA1
Configuring the Provider ID, License Type, and Deployment Scope
The first task in loading and using an SDK application is to configure the statements that describe the certificate. These statements include the provider ID, the type of certificate, and the scope of SDK application deployment. The provider ID is a prefix that is part of the certificate name used by the provider in building an SDK application. All three pieces of information must match the certificate used by the provider in building its SDK application if the router is to be enabled for installation of the provider’s SDK application. Configuring the certificate also turns on the SDK service daemon (ssd), which, by default, is off.
 | Note: Older certificates have all the certificate information concatenated in the provider-id statement. These older certificates are still supported, and you can install packages signed with them. |
To prepare the router for installation of a Junos SDK application, do one of the following:
- Configure the provider ID, the license type, and the deployment
scope for your application (consult your provider or application-specific
documentation for the correct values):[edit system extensions]user@host# set providers provider-id license-type license deployment-scope deployment
For deployment, there could be a series of values. For example, if abc is a provider ID issued to a provider with a commercial type of license and two deployment scopes:
[edit system extensions]user@host# set providers abc license-type commercial deployment-scope [ private commercial ] - If you have an older type of certificate, just configure
the provider ID (consult your provider or application-specific documentation
for the correct value):[edit system extensions]user@host# set providers provider-id
Multiple provider IDs can be enabled on a router. For example, if abc and xyz are provider IDs issued to two providers, then the following configuration enables the router for the SDK applications built by either provider. Notice that a provider can have more than one license and that each license can have multiple deployment scopes:
