We rely heavily on DUP_GROUP=UHD in our Flex licenses. The setting is applied to individual features. With this setting, when the same user on the same machine asks for multiple checkouts of the feature, the license server only makes the first checkout and somehow internally counts all the additional ones. When the user makes the last of all the check-ins, the server checks in the feature.
In Cryptlex we are using meter attributes for the licensed features and the allowed uses are the seat counts. So we would want something like a per-instance/per-machine/per-user switch on meter attributes. If the meter attribute is not set to per-instance, the server would need to check the machine/user (I’m hoping this info is in the fingerprint) and if there is already an active increment for this machine/user it would reference count it rather than make another increment. Decrements would have to do the reverse, decreasing any reference count before finally decrementing the meter.
Is something like this possible?