Rhinocommon Access to License key or Unique ID

Is it possible to access license key or Unique ID shown in Rhino Option>Licenses with Rhinocommon? I am trying to make a custom app/script that only works with pre-defined license keys. Thank you!

The RhinoApp makes a few properties like the user name and licensed user org available.
RhinoApp class (rhino3d.com)

The more conventional approach would be to package what you’re doing as a plugin, use the Cloud Zoo (guides at developer.mcneel.com) or other license scheme, examples at Robert McNeel & Associates · GitHub , and give keys to the users who are supposed to have them.

If you use the cloud zoo, you can even put a set of users into a group and let the group have a stack of licenses, which makes it easy to share to everyone within a company- kind of like Rhino does for lab licenses.

1 Like

Thank you Nathan,

I was able to pull up those information from RhinoApp class thanks. I think the other licensing control method using Cloud Zoo might be the one I also might have a look deeply. Appreciate your help!

I spent a good amount of time implementing the Cloud Zoo end to end a few months ago.

If you have any questions, let me know.

I also started to put together a few sets of implementation notes.

For your use case, one in particular might interest you. You don’t actually need to implement a Cloud Zoo server in order to license groups. (To unlicense them, you seem to need a server, but when it’s an internal tool you can just remove users from the group)

Here are some notes for Serverless Rhino Plugin Cloud Zoo Licensing for Groups

This works because the McNeel implemented optional end point for ADDing a license doesn’t call the server back: you say, with appropriate credentials, “McNeel, please add this license to that group.” and McNeel’s server says “OK”. Removing it does seem to require supporting the callback: you say “McNeel, please remove this license from that group.”, McNeel says “Hey, vendor API server, is removing this OK?” and not having a server available to answer that with “yes” causes a fail.

Because it does require your vendor credentials to create licenses and add them to McNeel’s server, this is a feature not a bug.

Related to that: two required steps, as spelled out in the Cloud Zoo guide, are getting credentials from William and Brian. William for an api key and password plus specifying where your server will be, and Brian for signing credentials as a vendor.

1 Like