serge Posted January 20, 2015 Report Share Posted January 20, 2015 Regarding the license manager plugin & "client trials" case,at doing a lot of test, I can see the license "status" echo on client side can only be :- "valid" if validor- "unknown" if other than validAnd real cases like, "expired licence", "suspended", "invalid_location" (when being ticked in blesta licence module), are only giving at client side an "unknown" statusSo in my script integration & my custom actions after license check, I'm only using "valid" case status or different of "valid" case status Quote Link to comment Share on other sites More sharing options...
serge Posted January 25, 2015 Author Report Share Posted January 25, 2015 I think what I reported above is maybe in connection to: in Blesta Table service_fields, for column "key" equal "license_module_status" - column "value" equal "reissue....." after the Blesta general cron when the order/service passed to active status. - column "value" equal EMPTY after the licence have been checked & validated by the licence check. Quote Link to comment Share on other sites More sharing options...
serge Posted January 28, 2015 Author Report Share Posted January 28, 2015 Will be glad to have feedback on that from people using the license manager plugin/module Quote Link to comment Share on other sites More sharing options...
serge Posted April 17, 2015 Author Report Share Posted April 17, 2015 will be glad bug report be followed/answered Quote Link to comment Share on other sites More sharing options...
vetal Posted April 22, 2015 Report Share Posted April 22, 2015 I have exactly the same issue. My blesta version is 3.4.3. License Module 1.5.1 PHP 5.3.3 I would like to have feedback from you. serge 1 Quote Link to comment Share on other sites More sharing options...
serge Posted April 28, 2015 Author Report Share Posted April 28, 2015 ok, thank to Vetal confirmation, I found strange no other found the same. I even saw the place in the code where I think it's wrong, it's the way a conditional is doing, it's will be always giving the default "unknown" answer when license Key is not "active" VS giving a detailed status like expired, etc.. PauloV 1 Quote Link to comment Share on other sites More sharing options...
Cody Posted April 28, 2015 Report Share Posted April 28, 2015 I think what I reported above is maybe in connection to: in Blesta Table service_fields, for column "key" equal "license_module_status" - column "value" equal "reissue....." after the Blesta general cron when the order/service passed to active status. - column "value" equal EMPTY after the licence have been checked & validated by the licence check. That is the desired behavior of the License Module. The license_module_status field will only contain "reissue" if the license is in a reissue state. If not in a reissue state, then it contains no data. serge and Michael 2 Quote Link to comment Share on other sites More sharing options...
Cody Posted April 28, 2015 Report Share Posted April 28, 2015 ok, thank to Vetal confirmation, I found strange no other found the same. I even saw the place in the code where I think it's wrong, it's the way a conditional is doing, it's will be always giving the default "unknown" answer when license Key is not "active" VS giving a detailed status like expired, etc.. I think you are referring to LicenseManager::validate() on line 155 of license_manager.php. That method only returns a status of unknown if no license data is given, or the license data signature is invalid. serge and Michael 2 Quote Link to comment Share on other sites More sharing options...
Cody Posted April 28, 2015 Report Share Posted April 28, 2015 Regarding the license manager plugin & "client trials" case, at doing a lot of test, I can see the license "status" echo on client side can only be : - "valid" if valid or - "unknown" if other than valid And real cases like, "expired licence", "suspended", "invalid_location" (when being ticked in blesta licence module), are only giving at client side an "unknown" status So in my script integration & my custom actions after license check, I'm only using "valid" case status or different of "valid" case status The expired status will only be provided if the last call-home is date is more than $ttl seconds past. Where $ttl is passed into LicenseManager::validate(). You'll only receive a suspended status if the service for the license is suspended in Blesta, and the client makes a call-home to fetch this update. This is one reason why you should perform at least a daily call-home. The invalid_location status is given if the IP, path, or domain of the client no longer matches the value stored in the encrypted license data stored on the client. Michael and serge 2 Quote Link to comment Share on other sites More sharing options...
serge Posted April 29, 2015 Author Report Share Posted April 29, 2015 Thanks for explanations. All is matching to what I did observe, and for info, my TTL is matching to 1 day (in second unit). Licence data & Public Key & licence Key are stored on client side. With call home once a day. From memory, only thing that do not match to what you describe is when location change I think it was the "unknow" status echoed at client side, so I will be re-testing that today Quote Link to comment Share on other sites More sharing options...
serge Posted April 29, 2015 Author Report Share Posted April 29, 2015 From memory, only thing that do not match to what you describe is when location change I think it was the "unknow" status echoed at client side, so I will be re-testing that today Just tested, and it's the "unknown" status returned client side when location changed Quote Link to comment Share on other sites More sharing options...
Cody Posted April 29, 2015 Report Share Posted April 29, 2015 Just tested, and it's the "unknown" status returned client side when location changed Really not sure how you could get that. You should only get the unknown status if the local license data can not be decrypted. When you receive the unknown status, what do you have stored for the license data on the client side? It should be the same data both before and after the client changes location before the next call home. serge 1 Quote Link to comment Share on other sites More sharing options...
serge Posted April 29, 2015 Author Report Share Posted April 29, 2015 ok, great explanation, thanks. I was wrong in my today test, there were data (licence_data, license_key, public_key) stored client side, but as my script alway call home once after a no active status is get from local license_data passed through the license check function, I was no echoing the license status before the call home, but my script had ever this option I missed to enable today. And when doing it, it's well returned the invalid_location status. THANK YOU! Quote Link to comment Share on other sites More sharing options...
Cody Posted April 29, 2015 Report Share Posted April 29, 2015 Glad I could help! Paul and serge 2 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.