Licensing question [SOLVED]

On 02/02/2017 at 11:25, xxxxxxxx wrote:

I Would like to ask more informations about how serial are build.

Firstly multiLicense. That mean each time user launch the software he can have a different serial?
I don't understand in the sdk the range of possible value.

Is it a way for managing serial location (if I'm right c4d allow a kind of subscription), I mean is it possible for a user to have the same serial after few subscription?

And how rlm license are working exacltly is it ike a single license or a multiLicense which can be random a each start?

Thanks in advance :)

On 03/02/2017 at 08:03, xxxxxxxx wrote:

Hi gr4ph0s, thanks for writing us.

First of all I'd recommend you the following links from Cineversity where multi-license licensing scheme is properly explained

• License Server Installation
• License Server Groups & Leasing
• License Server Assignment Options
• License Server Automatic Joining

and, to close the loop, those from our Blog where putting in place plugin licensing is properly presented:

• Part I – Basics
• Part II – License implementation
• Part III – Implementing the license validation
• Part IV – Implementing a key generator
• Part V – Extensions and improvements

Back to your question, is relevant to know that the client is provided with a license issued by the server every time Cinema is run or the lease period has expired. That said it's not necessarily granted that the license issued results different from time to time.
On top of that is also relevant to know that the leased license always belong to the bundle the group, where the client belong to, is assigned to.

I don't understand in the sdk the range of possible value.

What range are you referring to?

Is it a way for managing serial location (if I'm right c4d allow a kind of subscription), I mean is it possible for a user to have the same serial after few subscription?

What kind of subscription are you referring to?
More than about the user, I'd say that is pretty likely that a same client receives the same serial if it's available in the license pool.

And how rlm license are working exacltly is it ike a single license or a multiLicense which can be random a each start?

The RLM licensing schema is basically an alternative solution to provide a flexible licensing system like the MAXON License Server for multi-seat environment.

Looking forward your further comments, give best.

R.

On 04/02/2017 at 03:48, xxxxxxxx wrote:

Thanks for all the links you provide me.

In a case of multi license pool.
If I understand correctly, the license provided by GeGetSerialInfo(c4d.SERIALINFO_MULTILICENSE) will be identical each time. So I can read it and doing my crypto stuff with the one is written in my lic file and then check if the license number are identical?

On 05/02/2017 at 17:34, xxxxxxxx wrote:

Thanks for that guide,
but I have the same Gr4ph0s question.

thanks
Renato T.

On 06/02/2017 at 00:51, xxxxxxxx wrote:

Hi gr4ph0s/Renato,

the resulting serial obtained by using the GeGetSerialInfo() for a multi-license environment is  definitively expected to be identical from time to time.

Best, R.

On 06/02/2017 at 10:05, xxxxxxxx wrote:

Originally posted by xxxxxxxx

definitively expected to be identical from time to time.

So it's definitively or time to time? I excepted a yes or no answerd.

Sorry in my lack in english (need too improve it sadly) but anyway thanks for the reply:)

On 06/02/2017 at 13:46, xxxxxxxx wrote:

Basically we issue multilicenses as a "package" containing 2 serials - the standard C4D serial and the multilicense serial. The multilicense serial is linked to the C4D serial (digits 7-11 are identical), and specifies the number of licenses for the package.

So for any given serial package, the C4D serial and the multilicense serial will always be the same, and you can get them with GeGetSerialInfo(c4d.SERIALINFO_CINEMA4D) and GeGetSerialInfo(c4d.SERIALINFO_MULTILICENSE). If you want to key specifically to the number of seats, use SERIALINFO_MULTILICENSE, which indicates the seat count in digits 4-6.

In many cases, a single customer may have multiple serial packages - either because they were purchased separately or because they want to specify use counts and link plugins for specific users or departments. But really you as a plugin developer only need to worry about licensing one license per seat enabled in each multilicense.

The only time the multilicense number will change within a release cycle is if the customer purchases additional seats for that serial package, in which case digits 4-6 will change to show the new seat count.

So for instance, MAXON NEWS NETWORK may have 10 seats for their Broadcast department and 5 seats for the Online department. Those are two separate packages, and one will have a multilicense key with 010 in digits 4-6 and the other with 005 in digits 4-6. They might want to license your plugin for use in the Online department, and you'll key against the associated multilicense number with 005 in digits 4-6. That number will always stay the same for the release cycle, unless they increase the seat count (in which case, they need to purchase additional license(s) for the plugin.

I hope that makes sense.

On 06/02/2017 at 15:11, xxxxxxxx wrote:

Thanks you Rick Barret that make a lot more sense for me.

Then basicly SERIALINFO_CINEMA4D is to track one license so it's safe to use it for limit the usage of my plugin to 1 seat, and it will be always the same seat.

While the SERIALINFO_MULTILICENSE is to track a number of seats in the multilicense pool. So each user will have their own SERIALINFO_CINEMA4D  but will have all the same SERIALINFO_MULTILICENSE.

And finally if we read the sdk 201[100]00519-.
201[100]00519 is the SERIALINFO_CINEMA4D part.
ABCDEF is the SERIALINFO_MULTILICENSE part.

Thanks you a lot, you guys at support you are doing a great job ! Keep it going, it's very pleasant :)