How to restrict licence activation on back dated PC

[gajeshm]

Hello,

We are using Flexnet APIs to activate TS licence and checkout as well. If licence is activated on back dated PC, the licence verification (checkout) fails with error -31 (Start date for feature not reached).

The licence state is active and valid but licence verification fails, it make the problem identification difficult.

I was expecting licence verification to be successful in case of permanent licence and time bound licences to expire as per duration from activation date.

What should be done in this case, Should we restrict licence activation on back dated PC? If yes, How (offline and online)?

Any other suggestion?

Regards,

Gajesh

[mrathinam]

Hi @gajeshm the future start date of a feature can be activated using TS activation API but license validation will give an error 

--

Trust Flags: FULLY TRUSTED
Fulfillment Type: PUBLISHER ACTIVATION
Status: ENABLED
Fulfillment ID: FID_179f1b3e_009e_4519_8890_8f80c293a831
Entitlement ID: f917-c765-12e5-4636-bf87-addc-e54a-d879
Product ID: Thermo_UpgradeTS
Suite ID: NONE
Expiration date: permanent
Feature line(s):
INCREMENT 2DLine demo 1.0 permanent 1 ISSUER="My Corporation" \
ISSUED=14-feb-2022 START=15-feb-2022 SIGN="00B7 6979 5525 1798 \
0816 8D8D 19C0 0100 7EAB 4616 7534 0432 CFB7 FE13 17F8"

--

and this is expected behaviour in both certificate and TS licenses. 

--

16:53:06 (demo) Feature f1 is not enabled yet, starts on 15-feb-2022
16:53:06 (demo) License server system started on BLR-LT-101186
16:53:06 (demo) No features to serve, exiting
16:53:06 (demo) EXITING DUE TO SIGNAL 27 Exit reason 4

--

Best Regards,

[gajeshm]

Thanks Mani.

If licence can't be validated then why it is allowed to activate? Is there any scenario where we should let this happen?

[mrathinam]

Hi @gajeshm this is because we can give future date licenses to customers but the start date is where when they are entitled to use the application.  I don't think any other use case we have. 

Best Regards,