We are using our own DotNet application linked with the licence generation API from Sentinel LDK 7.3 to generate Sentinel SL-AdminMode licences. We have a problem in that we need to process licence requests twice in order to get a complete licence installed.
The licencing sequence is as follows:
1. On the initial run of our our distributed program we install a provisional licence with 1 product, 8 features, R/O and R/W memory entries.
2. The client generates a fingerprint file from within our application using hasp_get_info specifically requesting host_fingerprint.
3. We process the fingerprint file and generate a licence with 1 product, 1 or more features, R/O and R/W memory. The licence type is set to SNTL_LG_LICENSE_TYPE_FORMAT_AND_UPDATE (we previously tried using SNTL_LG_LICENSE_TYPE_UPDATE but changed in an attempt to solve our problem). The licence is generated via a call to sntl_lg_generate_license. We also store the resultant state.
4. The generated V2C licence is returned to the client who installs it using hasp_update.
5. The new licence on the client computer has the product and feature(s) specified but not the R/O and R/W memory which our application depends on for versioning.
6. The client generates a C2V file from within our application using hasp_get_sessioninfo specifically requesting updateinfo.
7. We process the C2V file and regenerate the same licence as per step 3.
8. The generated V2C licence is returned to the client who installs it using hasp_update.
9. The new licence on the client computer has the product and feature(s) specified as well as the R/O and R/W memory which our application depends on for versioning.
The process of having to request a licence update twice is understandably annoying our customers as they cannot work until the whole process is completed.
If we process the resultant state generated in step 3 as a c2v file then we see a licence specification which is correct as to how we would like it written, including the relevant R/O and R/W memory.