About TrinityTonic

jberthold · ‎Mar 23, 2023

Hi @TrinityTonic , My understanding is it does not pose any additional risks compared to the current Java-based server. I'd recommend opening a support ticket on this topic. Thanks, Jim

TrinityTonic · ‎Mar 20, 2023

Hi @jberthold - thanks! Yea that's what we are doing now. As we cannot have two license sources of the same type (trusted storage) inside a source collection we are now having two completely separate source collections. Now, whenever the user is acquiring a license, the functionality is wrapped and internally our licensing component will iterate over all existing source collections, switch the source environment (i.e. set the corresponding host and binding id and paths) and then perform the actual function. The same applies for all other licensing functionalities. FNE SDK does not offer having multiple host ids, binding ids and paths at the same time as the callbacks can only be set once. Thus the environment has to be setup accordingly before every licensing operation. One thing we first missed was that each source collection needs its own publisher object resource. That one cannot be shared between multiple sources - although one might think that the source collections could have the same publisher.

jberthold · ‎Mar 14, 2023

Hi @TrinityTonic , ** Updated Response ** The JNI code lives inside the Local License Server jar as resources, and is extracted on server startup. You can’t run on ARM because we don’t have a build of the JNI for that architecture, so the extraction fails and the server stops. Thx, Jim

jberthold · ‎Mar 13, 2023

Hi @TrinityTonic , With the clock windback frequency set to 1 day, the timestamp in the Trusted Storage anchor file will be updated once per day. The number of licenses in Trusted Storage will not have an impact. Note that processing a new capability response into Trusted Storage will also result in a timestamp update. Best regards, Jim

jberthold · ‎Mar 06, 2023

**Updated ** We are planning on releasing the new FLSM in the June 2023 timeframe. Availability may be made earlier for selected customers. Thanks, Jim

jberthold · ‎Mar 06, 2023

Yes it's in the FlexNet Operations User Guide https://docs.revenera.com/ and in the FNO online help. Production Endpoint URLs for FNO are shown below:

Stefan_Erucsir · ‎Feb 21, 2023

@TrinityTonic wrote: [...] Out of curiosity - why do you want to move from node-locked licensing to floating licenses? What's your current use-case for using node-locked and what would be the use-cases that require floating licenses? The reason for us to evaluate a license server based option are: Currently we use node-locked with a smart card based dongle as secure host ID source. So its node-locked to the dongle, which allows the customer to move his entitlements from one machine to another by physically moving the dongle (we permit that). However using the smart card based dongle has some limitations: Using a remote desktop connection to the machine that uses our licenses application is not possible, because Windows deactivates the local smart card on connection. And the other reason is, our application regularly checks whether the dongle is still present, however sometimes when our application does some number crunching, the IO to the dongle is blocked and then the application goes into a restricted mode (and the current operation is stopped). This can be very annoying to the user. And finally its also a logistical thing: the dongle needs to be shipped to the customer. Sometimes they loose it, and we need to provide a replacement which means re-issuing of licenses and a whole rat tail of administration to do. Over time we found that the level of security that the dongle provides is nice, but maybe a bit too much and we are willing to make a trade-off now. However just getting rid of the dongle and instead using a MAC address or similar as host ID source is also not so practical because this restricts the customer of using the application on multiple machines (we want to allow that; just not on multiple machines at the same time). And it feels its too easy to clone licenses with that. Hence we look into the license server option with floating licenses now. It allows the customer to easily move his entitlements from one machine to another. And it seems to provide a reasonable level of security through the capability requests/response so we can at least somewhat ensure that licenses are returned.

TrinityTonic · ‎Jan 31, 2023

We are using the Flexnet C SDK for licensing on our clients. We mostly perform offline licensing scenarios, where we upload a capability response manually to the device in order to distribute the required licenses. We have encountered a problem that we wanted to discuss. In case we upload a capability response file that has already been successfully used once a second time the internal C API function returns an error, namely FLXERR_RESPONSE_STALE. We want to adapt the functionality so that we only return an error inside our function if the capability response would change to a state of the licenses inside trusted storage, i.e. if licenses are removed / added. In case the capability response has already been processed, but if the response would not change (add or remove licenses) we do not want to return an error. Could you make a suggestion on how to implement this in a most efficient way using the C SDK API?

jberthold · ‎Jan 08, 2023

Hi @TrinityTonic , Device registration can be enabled to only allow feature requests to Cloud License Servers from registered devices. Please refer to the following video in the learning center for further details: https://learning.revenera.com/cloud-licensing-with-flexnet-operations-and-flexnet-embedded/601720 Thanks, Jim

jberthold · ‎Oct 10, 2022

Hi @TrinityTonic , Your diagrams are accurate if the FlexNet Operations Configuration setting for "Skip Confirmation" (found in System/Configure/Embedded Devices/License Generation) is disabled (not checked). With Skip Confirmation disabled, the device must prove to FNO that the capability response with the license reduction was indeed processed. So let's take a look at both scenarios (first let's assume that the device is offline and does not have an internet connection) 1. Return initiated in FNO Portal. a. The license is first removed from the device in the FNO Portal. The status of the license on the device in the portal will be set to "Waiting for confirmation". The license has not yet been credited back to the entitlement for use by another device. b. The capability response with the license removal is then downloaded from the FNO Portal and manually loaded onto the device. c. A confirmation capability request then needs to be generated from the device which will be used to prove to FNO that the capability response for the license reduction from FNO was processed on the device. This is sometimes called a "sync" capability request which is a standard activation request with no Activation ID or Quantity specified. d. Once generated, this sync capability request is then manually uploaded to the FNO Portal. This will remove the license from the device and free it up for use by another device. 2. Return initiated on Host. a. The device creates a capability request to return the existing license which includes the desired Activation ID with quantity 0. b. This capability request is then uploaded in the FNO Portal. The capability response with the license removal is downloaded from FNO and loaded on the device. c. A confirmation capability request then needs to be generated on the device and uploaded to the FNO portal to prove the capability response was loaded so the license can be freed up for use on another device. If the device has an internet connection the capability requests & responses can be done programmatically. If Skip Confirmation is enabled (checked) then you trust that the customer will always load the capability response file on the device when a license is returned. The license will immediately be freed up in FNO once the license is removed from the device in the FNO portal. This is not as secure and is a potential area for license abuse, however it prevents the need to generate and upload/send the additional confirmation request. This can be accomplished transparently if the device is online but requires additional manual steps if the device is offline. Best regards, Jim

Online Status	Offline
Date Last Visited	‎Mar 28, 2023 07:13 AM

Re: C-based (FNE) floating license server

Re: Multiple trusted storage sources (internal, dongle, ...)

Re: ARM support for local license server

Re: Best pratice regarding clock wind-back settings

Re: Access to FLSM - FlexNet License Server Manager

Re: Differences in requests to FNO and license server

Re: How do YOU hand over flexnetls to the customer?

Checking if a capability response would alter the device state

Re: Handling of Floating Licenses (borrow / renewal intervals, ...)

Re: Secure Return of Licenses

Re: C-based (FNE) floating license server

Re: C-based (FNE) floating license server

C-based (FNE) floating license server

Re: Multiple trusted storage sources (internal, dongle, ...)

Re: Multiple trusted storage sources (internal, dongle, ...)

Re: ARM support for local license server

Re: ARM support for local license server

ARM support for local license server

Re: Best pratice regarding clock wind-back settings

Best pratice regarding clock wind-back settings