Sentinel Hardware Keys Developer's Guide - Customer Connection ...

Secure Remote New License Addition
Contents Glossary Index Troubleshooting
4. In the Export-File Manager wizard, the developer selects Export a file
for License Addition. (Allows creation of *.NLF file), and clicks
Next.
5. The developer selects the Bidirectional mode from the Mode dropdown,
and clicks Next.
6. The developer browses and selects the request code (.req) file in the
Request Code File field. The request code file populates the Serial
Number and Device Update Counter 3 values in the respective
fields.
7. The developer may select the Delete all licenses from token check
box, if required, to remove all the licenses from the token.
Selecting this check box displays a warning, “This will remove all the
licenses from the token. Are you sure you want to do this?”. Click Yes to
confirm, and it removes all the existing licenses from your token,
before loading a new license.
8. The developer clicks Next to continue further in the wizard. After
defining a destination path in the File Name field, specifies the cheat
counter value in the Cheat Counter (only for non-RTC keys) field,
and then clicks Generate. The loadable license packets are generated
and exported in the form of *.nlf file.
9. The developer sends the license addition (*.nlf) file using an e-mail to
the customer.
10.The customer applies the license addition code to use the new license.
Unidirectional New License Addition
In this mode, the developer generates the new license addition code without
any request code from the end user. It is assumed that the Serial Number
and Device Update Counter is known to the developer.
3.The Device Update Counter, stored in the .req file in bidirectional mode, is needed when the
developer wants to delete all licenses from the Sentinel Key, before loading new licenses.
Sentinel Hardware Keys Developer’s Guide 147